ARTICLE AD BOX
We have a very large, and very old application written in ASP.NET Framework. We recently upgraded it to 4.8.1, rewrote it to use async/await, and removed all context dependencies such as HttpContext.Current. Everything uses DI now.
From our research, we know that .ConfigureAwait(false) does not benefit ASP.NET Core, but it can benefit ASP.NET Framework if the application is setup correctly.
So, hypothetically, if we mitigated issues caused by ConfigureAwait(false) by removing contextual variables, then should we use it everywhere? Or is this not the case anymore?
