Changing object property init value breaks hot reload

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[severity:It bothers me. A fix would be nice]
Follow-up for the already reported Blazor WASM HotReload Unexpected error.

I did nothing special, just added another C# object property initializer value.

The browser tab was opened on the other screen, previous HotReload changes have been applied without errors. Don't know what was special for this code edit.

The Websocket communication reported an "HotReload apply" error:

But the browser tab is still fully functional (just without the latest changes).

---

Original Comments

Feedback Bot on 7/25/2025, 04:54 AM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

[dotnet-policy-service]

Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal repro project that illustrates the problem without unnecessary code. Please share with us in a public GitHub repo because we cannot open ZIP attachments, and don't include any confidential content.