Blazor WASM: Publish from MSBuild does not create wwwroot\_framework folder

[Gambero81]

I use Visual studio 2019 v16.8.4

Create a new Blazor WASM app, and publish.

If i publish from visual studio all work well.

if i publish with MSBuild.exe, the publish wwwroot subfolder does not include the _framework folder and running the app fail with error 404.

i use this msbuild command:
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\MSBuild.exe" "%SolutionFilePath%" /t:Rebuild /p:Configuration=Release /p:DeployOnBuild=true /p:PublishProfile=Release /p:DebugSymbols=false /p:DebugType=None /p:AllowedReferenceRelatedFileExtensions=none /fl

in attachment a sample project to reply the issue,

What's wrong? i miss a msbuild parameter?
Thanks

BlazorApp18.zip

[javiercn]

@Gambero81 It's a bit strange that you are using full framework MSBuild to publish the app from the command-line.

Is there a reason why dotnet publish doesn't work for you? That's the recommended way to publish from the command-line and what we test for.

[Gambero81]

@javiercn the problem seem to be related to recent upgrade of my project to net5.

Publish with MSBuild with .net core 3.1 work well.

I will try doing it with dotnet publish and reply asap.

[pranavkm]

@Gambero81 could you use the Publish target instead of using /p:DeployOnBuild. Also I only tried publishing the Server project rather than the sln:

set SolutionFilePath=%ProjectPath%\BlazorApp18\Server\BlazorApp18.Server.csproj

set MSBuild=C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Current\Bin\MSBuild.exe
set MSBuildParameters="%SolutionFilePath%" /restore /t:Publish /p:Configuration=Release /v:M /p:PublishProfile=Release /p:DebugSymbols=false /p:DebugType=None /p:AllowedReferenceRelatedFileExtensions=none

It looks you get different sets of targets invoked when using /p:DeployOnBuild=true vs /t:Publish. Probably something to look in to.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[tai-yi]

Tried many times, details show in below, any idea?

Publish command dotnet publish -c release

• publish in solution folder, there is no _framework published in BlazorApp.Server output folder.
• publish in BlazorApp.Server folder, _framework is published in BlazorApp.Server output folder.
• dotnet publish BlazorApp\BlazorApp.Server -c release in solution folder, _framework is published in BlazorApp.Server output folder..

sln-folder
   app.sln (include all csproject)
- BlazorApp
      BlazorApp.Client (BlazorApp.Client.csproj)
      BlazorApp.Server (BlazorApp.Server.csproj)
- ApiApp2  (ApiApp2.csproj)