CLI Hot reload for Blazor wasm still doesn't work in .NET 7

[ziaulhasanhamim]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

#40587 was supposed to be fixed in .NET 7 with dotnet/sdk#27699. But there is still the same problem. Blazor wasm hot reload still breaks all the time

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

7.0.100

Anything else?

No response

[mkArtakMSFT]

@tmat can you please look into this? Thanks!

[jinzhao1127]

@mkArtakMSFT this issue looks like same as https://github.com/aspnet/AspNetCore-ManualTests/issues/885, it only reproes on the first time to execute dotnet watch

[ziaulhasanhamim]

In my case, it happens whenever the build takes a long to complete.

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[wocar]

It is still broken for me as well...

[wocar]

@tmat

Some race conditions were fixed, at least my browser launches now and the hot-reload capabilities verbose message seems correct, however:

└─$ dotnet --version      
7.0.102

		<PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="7.0.2" />