Expected Behavior / New Feature

As stated in the ReadMe, Ocelot depends on .net standard 2.0 and should be usable with full .net framework

Actual Behavior / Motivation for New Feature

Nuget states that Ocelot 14.0.9 depends on .net core 3.1

I want to extract string from PDF. How to achive it with this library.
PDFTextExtractor class from PdfSharp seems to be missing.

Unless there is a good reason to have the thread SynchronizationContext preserved, all of your await ...calls throughout the library should have .ConfigureAwait(false) appended.

Not having this causes deadlocks when having to call your library in a synchronous manner such as:
var meta = ffmpeg.GetMetaDataAsync(input).GetAwaiter().GetResult();

Obviously you would ideally not call it

The REST API that Checks user existence in a group always returns an empty body.

This issue occurs in both of the Check user existence in a group REST APIs:

• https://.service.signalr.net/api/v1/hubs//users//groups/
• https://.ser

The package lacks some documentation, that makes it hard to use. For example, when adding the Elmah service, there is no clue about the meaning of the option fields.

Is it possible to add a summary tag to the public items? That would greatly help to use this library.

Hi,

We leveraged these libraries around three/four years ago to help us build LTI Tools and it's served us well. I'm now reviewing our LTI Tool framework and wanted to leverage the newer version of this as we plan to begin hosting our LTIs in the cloud and leverage Angular etc.

Something that has not changed though is the contents of the projects' README files, the simply contain a single l