standards-c-sharp

Correct use of ConfigureAwait(false)

• In legacy ASP.NET code, if you must block on an asynchronous call, use ConfigureAwait(false) to avoid deadlocks.
• In library code (ie. code that could be consumed by arbitrary callers), always call ConfigureAwait(false).
• In .NET Core, do not use ConfigureAwait(false) as it has no effect.
• To emphasize: using ConfigureAwait(false) to avoid deadlocks should be considered a hack. If possible, rewrite the code so blocking is not required.
• Further reading:
  • https://medium.com/bynder-tech/c-why-you-should-use-configureawait-false-in-your-library-code-d7837dce3d7f
  • https://stackoverflow.com/questions/13489065/best-practice-to-call-configureawait-for-all-server-side-code

This site is open source. Improve this page.