ghost
commented
1 year ago 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: | - |
maraf
Repro:
dotnet new blazorwasmdotnet publish -c Releasecd bin/Release/net8.0/publishlsExpected:
web.configwwwroot/Actual:
dotnet.native.wasmweb.configwwwroot/This spurious
dotnet.native.wasmfile is not used for anything here (there's another, correct copy of it insidewwwroot/_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 thatwwwrootis 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.