Publishing blazorwasm template project is broken with the latest SDK
See original GitHub issueDescribe the bug
New Blazor WASM template projects don’t work after publish.
To Reproduce
- Install 5.0.100-rc.1.20427.6 SDK from https://github.com/dotnet/installer#installers-and-binaries
dotnet new blazorwasm
dotnet publish -c Release
- Try to run the published app
Expected results
The app loads correctly
Actual results
The app sits at:
Further technical details
Looking at the output of the publish directory, it appears non of the ASP.NET assemblies are being published:
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Failure to publish WASM when project source path ...
Even a simple publish to folder fails with error message: C:\Program Files\dotnet\sdk\6.0.301\Sdks\Microsoft.NET.Sdk.BlazorWebAssembly\targets\ ...
Read more >blazor hosted template project not working after publishing ...
Blazor WASM Hosted project has three projects: client, server and shared. To publish the solution as a one publish site, run the command...
Read more >Host and deploy ASP.NET Core Blazor WebAssembly
Learn how to host and deploy Blazor WebAssembly using ASP.NET Core, Content Delivery Networks (CDN), file servers, and GitHub Pages.
Read more >How to fix Blazor WASM base path problems - elmah.io Blog
This post will show you how to fix a common problem when setting the application base path with Blazor WebAssembly.
Read more >Blazor Hero - Clean Architecture Template Quick Start Guide
In this article, we will learn about getting started with Blazor Hero - A Clean Architecture Template built for Blazor WebAssembly using MudBlazor ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve added a commit to #13093 which should fix this issue.
Can you provide the earliest SDK version that has this issue? I’ll look into why they may have missed this.