Figure out whether project system should be using ConfigureAwait(true/false) on its await calls
See original GitHub issueFrom @davkean on November 13, 2015 20:51
We’ve currently suppress all usages of RS0003 in the project system code:
Warning RS0003 Do not directly await a Task without calling ConfigureAwait
We should review all instances of the suppressed values and figure out if we want ConfigureAwait(true)
or ConfigureAwait(false)
.
Copied from original issue: dotnet/roslyn#6770
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Should I use ConfigureAwait(true) or ConfigureAwait(false)?
This is where we set 'ConfigureAwait' to true or false to decide which thread the continuation task executes on. If we set ...
Read more >c# - Why is writing ConfigureAwait(false) on every line with ...
As a general rule, yes. ConfigureAwait(false) should be used for every await unless the method needs its context.
Read more >ConfigureAwait FAQ - .NET Blog
ConfigureAwait (false) involves a task that's already completed by the time it's awaited (which is actually incredibly common), then the ...
Read more >.NET: Don't use ConfigureAwait(false) | Gabe's Code
I've seen this advice all over: As a general rule, ConfigureAwait(false) should be used for every await unless the method needs its context....
Read more >Async, Await, and ConfigureAwait – Oh My!
ConfigureAwait (false) on every async call through the entire call stack! If you don't, you'll end up with another deadlock.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
All ConfigureAwait calls have been removed.
Above PR fixes the ConfigureAwait(true) states, and removes the analyzer. Further PRs needed to remove ConfigureAwait(false) cases if possible, as each is reviewed.