Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Default Blazor WebAssembly publish now outputs dotnet.native.wasm in wrong place #89031

Closed
SteveSandersonMS opened this issue Jul 14, 2023 · 2 comments
Closed

Default Blazor WebAssembly publish now outputs dotnet.native.wasm in wrong place #89031

SteveSandersonMS opened this issue Jul 14, 2023 · 2 comments
Assignees
@maraf
Labels
arch-wasm WebAssembly architecture area-Build-mono
Milestone
8.0.0

Comments

@SteveSandersonMS
Copy link
Member

SteveSandersonMS commented Jul 14, 2023 •
edited
Loading

Repro:

  • dotnet new blazorwasm
  • dotnet publish -c Release
  • cd bin/Release/net8.0/publish
  • ls

Expected:

  • web.config
  • wwwroot/

Actual:

  • dotnet.native.wasm
  • web.config
  • wwwroot/

This spurious dotnet.native.wasm file is not used for anything here (there's another, correct copy of it inside wwwroot/_framework) and is confusing as you would think you have to deploy this to your production server somewhere, but it's super unclear how you'd do that given that wwwroot is the actual output root as far as static file hosting is concerned.

I don't know whether this is a regression in the BlazorWebAssembly SDK or whether it's a runtime SDK issue.
@danroth27 danroth27 transferred this issue from dotnet/aspnetcore Jul 17, 2023
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jul 17, 2023
@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jul 17, 2023
@radical radical added arch-wasm WebAssembly architecture area-Build-mono labels Jul 17, 2023
@ghost
Copy link

ghost commented Jul 17, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Repro:

  • dotnet new blazorwasm
  • dotnet publish -c Release
  • cd bin/Release/net8.0/publish
  • ls

Expected:

  • web.config
  • wwwroot/

Actual:

  • dotnet.native.wasm
  • web.config
  • wwwroot/

This spurious dotnet.native.wasm file is not used for anything here (there's another, correct copy of it inside wwwroot/_framework) and is confusing as you would think you have to deploy this to your production server somewhere, but it's super unclear how you'd do that given that wwwroot is the actual output root as far as static file hosting is concerned.

I don't know whether this is a regression in the BlazorWebAssembly SDK or whether it's a runtime SDK issue.

Author: SteveSandersonMS
Assignees: -
Labels:

arch-wasm, untriaged, area-Build-mono, needs-area-label
Milestone: -

@radical radical added this to the 8.0.0 milestone Jul 17, 2023
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Jul 17, 2023
@radical radical removed the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jul 17, 2023
@maraf
Copy link
Member

maraf commented Jul 17, 2023

Duplicate of #88142

@maraf maraf closed this as not planned Won't fix, can't repro, duplicate, stale Jul 17, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Aug 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@maraf maraf

Labels
arch-wasm WebAssembly architecture area-Build-mono
Projects
None yet
Milestone
8.0.0
Development

No branches or pull requests
3 participants
@radical @SteveSandersonMS @maraf