This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work]
Steps:
- Create a new Blazor Web App project (all defaults, per-component, InteractiveAuto)
- Debug the project - Counter page works as expected, stop debugging
- Edit Counter.razor to wrap the button in an
@if (RendererInfo.IsInteractive) block
- Debug the project - Counter page never reloads into interactive mode; browser console shows:
Failed to load module script: Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of "". Strict MIME type checking is enforced for module scripts per HTML spec.
blazor.web.ax6tuj8tun.js:1 Uncaught (in promise) TypeError: Failed to fetch dynamically imported module: https://localhost:7075/_framework/dotnet.v7cin7japk.js
Workaround:
Do a full clean between debug sessions - Visual Studio is somehow leaving old/bad artifacts in the build tree.
Original Comments
Feedback Bot on 18/03/2026, 01:20 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.
Daniel Roth [MSFT] on 19/03/2026, 06:20 PM:
Thanks for reporting this issue! Do you see this problem only in VS and when debugging? Does the problem still happen if you run without debugging? What if you run the app using only the .NET CLI (dotnet run)?
Feedback Bot on 19/06/2026, 11:01 AM:
Thank you for taking the time to share your feedback. While we strive to address as many reported issues as possible, we have to prioritize based on overall impact and available engineering capacity. This issue hasn’t received much recent activity, votes, or comments in the past 90 days, and based on user engagement, severity, and current priorities, it is unlikely to be addressed in the near term. If this issue is still affecting and blocking you or your team, sharing additional updates or details about its impact, and encouraging others who are affected to vote or comment, can help increase the signal on this issue and allow us to reassess its priority.
This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work]
Steps:
@if (RendererInfo.IsInteractive)blockWorkaround:
Do a full clean between debug sessions - Visual Studio is somehow leaving old/bad artifacts in the build tree.
Original Comments
Feedback Bot on 18/03/2026, 01:20 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.
Daniel Roth [MSFT] on 19/03/2026, 06:20 PM:
Thanks for reporting this issue! Do you see this problem only in VS and when debugging? Does the problem still happen if you run without debugging? What if you run the app using only the .NET CLI (
dotnet run)?Feedback Bot on 19/06/2026, 11:01 AM:
Thank you for taking the time to share your feedback. While we strive to address as many reported issues as possible, we have to prioritize based on overall impact and available engineering capacity. This issue hasn’t received much recent activity, votes, or comments in the past 90 days, and based on user engagement, severity, and current priorities, it is unlikely to be addressed in the near term. If this issue is still affecting and blocking you or your team, sharing additional updates or details about its impact, and encouraging others who are affected to vote or comment, can help increase the signal on this issue and allow us to reassess its priority.