I have a [bad] habit of using .ConfigureAwait(false) when performing any and all async/await calls.
In some cases this is of course good because the vast majority of the time I don't care which thread the code continues on. In some cases I of course need it to continue on the same thread for specific reasons so either I don't use it or make sure the code is on the needed thread.
However, in Blazor does it matter if I call "UI" actions like StateHasChanged() using InvokeAsync()?
Does ConfigureAwait(false) itself even matter in the context of Blazor server or client-side development?