dotnet 9, "dotnet watch" is really bad in Blazor Server

[qucee98]

Environment:

• OS: Linux Ubuntu 24.04.1 LTS
• IDE: Vim/Neovim (non vscode and visual studio IDE)
• SDK: 9.0.200-preview.0.24575.35
• LSP: Omnisharp

hot reloading just sucks in dotnet 9 when using Blazor Server... 🤷‍♂️

I migrated my project from .net 8 to .net 9 and followed this doc:

• Static asset delivery optimization
• Improved server-side reconnection experience

dotnet watch command seems to be inconsistent in reloading the page when making changes to my current buffer.
When it starts to NOT work, then it never works after any changes, i have to restart the project manually.

".NET 9.0.200" patched it a bit, but hot reloading is still inconsistent in reloading the changes.
#44912
#45749
#45097
#45131

"Hot Reloading"? more like "Hot Mess".

Switching back to .NET 8 until y'all get your stuff together....

[XorZy]

It would be nice if Microsoft could acknowledge this problem and provide a clear ETA for the fix.
As it stands hot reload, which I would argue is essential when working with Blazor apps, is completely broken.
I have to restart the application every time I make the slightest of changes.
NET 9 was first released almost two months ago now, and I don't understand why fixing this issue is not a priority.