Blazor WASM don't really build

[vsfeedback]

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

---

[severity:I'm unable to use this version] [regression] [worked-in:17.13.6]
Since VS 17.14.0, any modification I do on .razor files are not compiled (no change visible when I launch the app) and after a rebuild, I can't launch the app at all (Blazor can't find the app .pdb, I get a 404 error and Blazor WASM can't finish its loading inside the browser).

A rollback to 17.13.6 fixed that (but make me lose all my VS configurations and extensions installed :( ).

---

Original Comments

Feedback Bot on 5/19/2025, 10:11 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.

[javiercn]

Thanks for contacting us.

Can you check what .NET SDK version are you using? Does it work if you rebuild and run from the command line (or if you make a change from the command line and run)

[dotnet-policy-service]

Hi @@vsfeedback. 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.

[dotnet-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.