ARTICLE AD BOX
I'm working on a C# application and have encountered situations where I'm not sure if I should be using ConfigureAwait(false) on my await calls. I've read some documentation, but the practical implications and potential pitfalls are still unclear.
I know that:
ConfigureAwait(false) tells the await expression not to try and capture the current synchronization context.But, are there specific examples where omitting it will definitely cause problems?
Take this for example:
public class MyLibraryService { public async Task<string> GetDataAsync() { using (var client = new HttpClient()) { // Should I add ConfigureAwait(false) here? var response = await client.GetStringAsync("https://example.com"); return response.ToUpper(); } } }If this library is consumed by a UI application, what are the implications of await client.GetStringAsync(...) versus await client.GetStringAsync(...).ConfigureAwait(false)?
I've looked at MSDN documentation and various blog posts. Some say "always use it in libraries," others say "only when necessary." This is where the confusion lies.
