[wasm] wasm-experimental: dotnet publish with output directory doesn't put the AppBundle in the output directory

[lambdageek]

.NET 8 Preview 2

$ dotnet new wasmbrowser
$ dotnet publish -c Release -o pub
...

What I expect:

The pub directory contains index.html, dotnet.wasm, etc. The stuff that normally would end up in bin/Release/net8.0/browser-wasm/AppBundle/

What actually happens:

The pub directory contains libmonosgen-2.0.a, pinvoke.c, runtime.es6.iffe.js, etc...

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

Issue Details

---

.NET 8 Preview 2

$ dotnet new wasmbrowser
$ dotnet publish -c Release -o pub
...

What I expect:

The pub directory contains index.html, dotnet.wasm, etc. The stuff that normally would end up in bin/Release/net8.0/browser-wasm/AppBundle/

What actually happens:

The pub directory contains libmonosgen-2.0.a, pinvoke.c, runtime.es6.iffe.js, etc...

Author:	lambdageek
Assignees:	-
Labels:	arch-wasm, untriaged, area-Build-mono
Milestone:	-

[lambdageek]

/cc @radical

[maraf]

This will be solved with taking over blazor sdk bits in #70762

[lewing]

I believe this is fixed now

[maraf]

It will be fixed once we move our templates to WasmSDK. I'll close the issue, since there is no extra work needed