You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 24, 2020. It is now read-only.
If WPF or other UI developers don't like this warnings they can always disable this analizer... or use .ConfigureAwait(true) to silence it if 99% of other await have to use .ConfigureAwait(false).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Libraries writers who use async/await (e.g. roslyn) use almost always .ConfigureAwait(false). I this case it would make sense to have some analizer like this: http://blog.cincura.net/233476-checking-for-configureawait-false-automatically/
If WPF or other UI developers don't like this warnings they can always disable this analizer... or use .ConfigureAwait(true) to silence it if 99% of other await have to use .ConfigureAwait(false).
The text was updated successfully, but these errors were encountered: