I've been using Blazor/Razor for a while and I have to say that I will generally be avoiding it moving forward.<p>It is really sad to me that the VS2022 experience around hacky, PHP-style string interpolation (e.g. @$"<html>{site goes here}</html>") is <i>far</i> superior to the experience of editing cshtml-style files exactly as prescribed by the vendor.<p>I've got some razor components that will simply crash VS2022 about 25% of the time. They aren't particularly large components, but you can <i>feel</i> some monumental, visceral amount of inertia behind these file types every time you try to work with them in the official editor.<p>Maybe dev experience is better over in vscode land, but I don't really care. There are enough other downsides to this web ecosystem to generally avoid it.<p>To be clear - I otherwise absolutely love everything .NET/C#/AspNetCore. Blazor and UI (MAUI) are their only real weak points, IMO. If you are willing to get your hands a little dirty as described above, you can sidestep entire mountains of depreciable chaos.