.NET 10 Preview 6 brings JIT improvements, one-shot tool execution

Re:.NET 10 Preview 6 brings JIT improvements, one-shot tool ... by bob1029 on Wednesday July 30, 2025 @09:59AM (#44734315)

> It’s so aggravating because ASP.NET with server side Blazor components really has it all

Agreed. I bailed on Blazor over the tooling experience. Editing components in VS2022 was so janky for me. Syntax highlighting and intellisense never worked correctly.

[ Parent | on HN ]

Re:.NET 10 Preview 6 brings JIT improvements, one-shot tool ... by MortyWaves on Wednesday July 30, 2025 @11:16AM (#44735345)

I don’t think there’s ever been any good tooling for the entire collection of ASP.NET DSLs. Be that MVC, Razor, or Blazor. Genuinely the same problems I had in VS2010 still happen in VS2022.

There’s been some changes and improvements, but I really have to ask what the editor tooling team within that team are doing.

I know there are some very difficult problems involved in parsing and formatting and highlighting bastardised mixtures of HTML, C#, and JavaScript all in the same file but if anything I think that perhaps suggests it was a bad idea to begin with.

Consider the tooling for desktop and mobile apps with XAML (WPF, Avalonia) or even WinForms - they all have code behind support.

Meaning there is no need (or ability) to mix all three in the same file.

[ Parent | on HN ]

Re:.NET 10 Preview 6 brings JIT improvements, one-shot tool ... by jabart on Wednesday July 30, 2025 @10:24AM (#44734655)

We have had great success with Maui Blazor Hybrid. Each release hot reload gets better with fewer edge cases. I also found that having a separate .cs file instead of in one file helps with highlighing and intellisense.

[ Parent | on HN ]