Hot reload using dotnet watch doesn't work 98% of the time

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

My colleges and I use Macs and the .NET CLI for development. Our solution contains two Blazor Wasm hosted apps and a .NET Web API. There are 4 of us and in the past month only 2 of us have seen hot reload work and that was for a grand total of two days.

Running dotnet watch -v shows the following: watch : Hot reload capabilities: . which I’m sure I read somewhere is not a good sign?

I appreciate this isn’t much to go on and I’d love to provide more information but I’m not sure what. But I’m happy to provide any other details.

Expected Behavior

Hot reload should work more than not.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

6.0.101

Anything else?

No response

[chrissainty]

@pranavkm So good and bad news. I installed the nightly build (6.0.201) and hot reload started working… for a day or two. But I’m back to Hot reload capabilities: .. Are there anymore details or things I can try?

[pranavkm]

The installers in the nightly build aren’t signed so it’ll print scary messages. Usually on Windows there’s a way to ignore it, but I’m not familiar with the MacOS equivalent. That said, I usually grab the zip archive and run dotnet from the extracted directory. That doesn’t have any of these issues.