.NET 10 Preview 6 brings JIT improvements, one-shot tool execution
1–10 of 231 posts
Re: .NET 10 Preview 6 brings JIT improvements, one-shot tool execution
#2All I want is for dotnet watch to behave in a predictable way. In .NET 9, even when using —no-hot-reload, sometimes CSS changes to components are not picked up on Blazor components.
It’s so aggravating because ASP.NET with server side Blazor components really has it all: type safety, server-side components ala Astro, fantastic ORM model, great runtime perf. But this little issue makes dev quite tedious at present: did I mistype a Tailwind class name, or did dotnet watch miss the change?
Re: .NET 10 Preview 6 brings JIT improvements, one-shot tool execution
#3All I want is for dotnet watch to behave in a predictable way. In .NET 9, even when using —no-hot-reload, sometimes CSS changes to components are not picked up on Blazor components. It’s so aggravating because ASP.NET with server side Blazor components really has it all: type safety, server-side components ala Astro, fantastic ORM model, great runtime perf. But this little issue makes dev quite tedious at present: di…
[flagged]
Re: .NET 10 Preview 6 brings JIT improvements, one-shot tool execution
#4All I want is for dotnet watch to behave in a predictable way. In .NET 9, even when using —no-hot-reload, sometimes CSS changes to components are not picked up on Blazor components. It’s so aggravating because ASP.NET with server side Blazor components really has it all: type safety, server-side components ala Astro, fantastic ORM model, great runtime perf. But this little issue makes dev quite tedious at present: di…
> 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.
Re: .NET 10 Preview 6 brings JIT improvements, one-shot tool execution
#5Might be worth viewing the full list of changes in the blog post that the article links to:
Re: .NET 10 Preview 6 brings JIT improvements, one-shot tool execution
#6All I want is for dotnet watch to behave in a predictable way. In .NET 9, even when using —no-hot-reload, sometimes CSS changes to components are not picked up on Blazor components. It’s so aggravating because ASP.NET with server side Blazor components really has it all: type safety, server-side components ala Astro, fantastic ORM model, great runtime perf. But this little issue makes dev quite tedious at present: di…
Are you using Visual Studio or another tool (vscode, vim, rider)? I found hot reload works a lot better in Visual Studio than any other IDE
Re: .NET 10 Preview 6 brings JIT improvements, one-shot tool execution
#7Might be worth viewing the full list of changes in the blog post that the article links to: https://devblogs.microsoft.com/dotnet/dotnet-10-preview-6/
Also, if you want to see the full list of changes in .NET 10 (not just the latest preview), you can find it here:
https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotn...
Re: .NET 10 Preview 6 brings JIT improvements, one-shot tool execution
#8All I want is for dotnet watch to behave in a predictable way. In .NET 9, even when using —no-hot-reload, sometimes CSS changes to components are not picked up on Blazor components. It’s so aggravating because ASP.NET with server side Blazor components really has it all: type safety, server-side components ala Astro, fantastic ORM model, great runtime perf. But this little issue makes dev quite tedious at present: di…
> 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.
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.
Re: .NET 10 Preview 6 brings JIT improvements, one-shot tool execution
#9All I want is for dotnet watch to behave in a predictable way. In .NET 9, even when using —no-hot-reload, sometimes CSS changes to components are not picked up on Blazor components. It’s so aggravating because ASP.NET with server side Blazor components really has it all: type safety, server-side components ala Astro, fantastic ORM model, great runtime perf. But this little issue makes dev quite tedious at present: di…
[flagged]
Say more?
Re: .NET 10 Preview 6 brings JIT improvements, one-shot tool execution
#10All I want is for dotnet watch to behave in a predictable way. In .NET 9, even when using —no-hot-reload, sometimes CSS changes to components are not picked up on Blazor components. It’s so aggravating because ASP.NET with server side Blazor components really has it all: type safety, server-side components ala Astro, fantastic ORM model, great runtime perf. But this little issue makes dev quite tedious at present: di…
Are you using Visual Studio or another tool (vscode, vim, rider)? I found hot reload works a lot better in Visual Studio than any other IDE
That's true, but even in Visual Studio, Hot Reload breaks too often to be comfortable. It seems the intermediate .g.cs handling is a bit error prone.