2 ms·
ConfigureAwait (mostly) no longer applies. You might want it in .NET 4.x apps, and in libraries that might be used in them. Or in apps with a "UI thread" - i.e.
by SideburnsOfDoom 4y ago
ConfigureAwait (mostly) no longer applies. You might want it in .NET 4.x apps, and in libraries that might be used in them.
Or in apps with a "UI thread" - i.e. desktop GUIs.
In modern ASP .NET, it does nothing, so we don't use it.
https://stackoverflow.com/questions/42053135/configureawaitfalse-relevant-in-asp-net-core https://stackoverflow.com/questions/42053135/configureawaitf...
- chrisoverzero 4y agoYour advice is correct for ASP.NET Core (the web application framework), but not for all of .NET (Core or suffixless).
- SideburnsOfDoom 4y agoThanks, I have edited. Even inside .NET different people work on very different things, and my niche might not be your niche.
- sebazzz 4y agoNot even (fully) for ASP.NET Core, as Blazor Server does use a SynchronizationContext.