ASP.NET Core does have a SynchronizationContext when using Blazor

[Sebazzz]

Avoid using Task.Result and Task.Wait:

AspNetCoreDiagnosticScenarios/AsyncGuidance.md

Line 232 in 0c82fa8

:bulb:**NOTE: ASP.NET Core does not have a `SynchronizationContext` and is not prone to the deadlock problem.**

ASP.NET Core Blazor does appear to use a synchronization context, being the RendererSynchronizationContext](https://source.dot.net/#Microsoft.AspNetCore.Components/Rendering/RendererSynchronizationContext.cs,11).

[davidfowl]

It does! Specifically, in Blazor Server when executing razor components (I should probably change that now).

[Sebazzz]

Yup, I should have specifically mentioned Blazor Server. This SynchronizationContext implementation doesn't necessarily schedule the work on the same thread like the WPF, WinForms and legacy ASP.NET does. It is prone to the same blocking issues however, I think.