Use ConfigureAwait(false) where applicable

[RevZero]

Consider best practice for general-purpose library code is to use ConfigureAwait(false) on all async calls.
This is used to avoid the callback to be invoked on the original context. This can avoid deadlocks from application code and improve performance.

Currently, the library doesn't use ConfigureAwait(false) anywhere.

[tinohager]

For .NET 8 web projects, this statement is not as relevant as it used to be. In modern ASP.NET Core applications (since .NET Core 3.0 and later), there is no SynchronizationContext, as ASP.NET Core uses a thread-free model.

Your statement is certainly correct in relation to Winform and WPF projects.

[RevZero]

As you pointed out, it is relevant for Winforms and some other project types. This is why its considered best practice to use ConfigureAwait(false) for libraries, because it might be used in environments with a SynchronizationContext.

I am not aware of any drawbacks, so I thought this would be something to consider.