Blazor WASM Hot Reload cli not working

[chhinsras]

I have blazor hosted. I run dotnet watch inside server project. Only hot reload works for sever project not the client project.

I try to run dotnet watch inside project. It has hot reload on client project when I change file, and of course there is no server running.

@chhinsras Can you file a new issue specifically about your Blazor WASM + hot reload problem?

Originally posted by @captainsafia in #38103 (comment)

[mkArtakMSFT]

Thanks for contacting us. Can you please share more context about the scenario in this issue so that everyone who will be reading this won't need to go to the linked issue and get the details from there?

Hi @chhinsras. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[chhinsras]

I have blazor hosted. I run dotnet watch inside server project. Only hot reload works for sever project not the client project.

I try to run dotnet watch inside project. It has hot reload on client project when I change file, and of course there is no server running.

[SteveSandersonMS]

@pranavkm Does watch handle ASP.NET Core-hosted WebAssembly projects?

[pranavkm]

It does. There is a (concurrency) issue with watch where it'll sometimes timeout and get incorrect hot reload capabilities for a Blazor WASM app, but in general, it should work.

[ziaulhasanhamim]

@pranavkm generally it doesn't work. once in a while it works.

[mkArtakMSFT]

@pranavkm is this a dupe then of the linked issue?