Add some .ConfigureAwait(false) to remove pressure on a sync context when available
Motivation for our WPF application:
We experience a lot of work and pressure on the UI thread due to the current handling of async calls to a remote data portal.
With this PR that should be solved because the low level operations are now free to use a thread pool thread to perform non UI related work.
The PR only adds .ConfigureAwait(false); to awaits where the result can't be known to the UI thread.
@rockfordlhotka Should we consider this a breaking change?
Add some .ConfigureAwait(false) to remove pressure on a sync context when available
Motivation for our WPF application: We experience a lot of work and pressure on the UI thread due to the current handling of async calls to a remote data portal. With this PR that should be solved because the low level operations are now free to use a thread pool thread to perform non UI related work. The PR only adds
.ConfigureAwait(false);toawaits where the result can't be known to the UI thread.@rockfordlhotka Should we consider this a breaking change?