Skip to content

CANNOT Publish Blazor WASM Apps to Folder using VS2026 #64128

@vsfeedback

Description

@vsfeedback

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


[severity:I'm unable to use this version]
I can't use VS2026 to publish my blazor wasm app to a folder at all. In my attempts and experiments compared between vs2022 and vs2026, every version of dotnet blazor wasm app cannot work in vs2026, so I consider that is a bug of vs2026, not of dotnet10rc2. Both VS2022 and VS2026 are latest.
To reproduce the problem, follow this:

  1. Install VS2022 and VS2026 with ASP.NET/Web Development feature.
  2. Use VS2026 to make a new project from templete Blazor WebAssembly with dotnet8~dotnet10.
  3. Go to VS2022 and open projects with dotnet8 or dotnet 9, and use the publish selection to publish this project to a folder, do same in VS2026, just have a more choice with project with dotnet10.
  4. Compare the wwwroot _frameworks folder generated by vs2022 and vs2026.

After this you should find that VS2026 only has serveral files in _frameworks, and VS2022 has the whole runtime. I think because of this difference, Cloudflare Pages run into a different condition. The web app generated by VS2022 runs well but generated by VS2026 has errors about mono_wasm_load_runtime () failed or MIME type or others.
I find this by comparing a single project, Blazor WebAssembly App with dotnet9, published by VS2022 and VS2026 then upload to Cloudflare Pages. Only VS2022 could run well.


Original Comments

Feedback Bot on 10/21/2025, 05:40 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Author: Migration Bot 🤖The issue was created by a issue mover bot. The author may not be the actual author.area-blazorIncludes: Blazor, Razor Components

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions