[wasm] wasmconsole - output path passed to dotnet publish does not result in a runnable project at the published path

[JakeYallop]

Description

Related to #94291

dotnet publish always outputs actual runnable output to the AppBundle directory (technically, $(WasmAppDir)) - this means that if I pass a custom path when running dotnet publish, e,g dotnet publish -o "C:/myCustomPublishLocation", the location, although it seems like something has been built there (it seems to match the contents of the browser-wasm folder), it is missing key files such as the blazor.boot.json.

This does not seem to be a very good experience for anyone attempting to customise the behaviour of a publish.

Its possible this issue might be a better fit in dotnet/sdk - I'm not sure where the targets are actually located.

Reproduction Steps

dotnet new wasmconsole
dotnet publish -o "C:/publishLocation"

Expected behavior

The output written to "C:/publishLocation" is the published files for the project.

Actual behavior

The output written to "C:/publishLocation" does not contain all the files required to actually run the project.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

[ghost]

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

Issue Details

---

Description

Related to #94291

dotnet publish always outputs actual runnable output to the AppBundle directory (technically, $(WasmAppDir)) - this means that if I pass a custom path when running dotnet publish, e,g dotnet publish -o "C:/myCustomPublishLocation", the location, although it seems like something has been built there (it seems to match the contents of the browser-wasm folder), it is missing key files such as the blazor.boot.json.

This does not seem to be a very good experience for anyone attempting to customise the behaviour of a publish.

Its possible this issue might be a better fit in dotnet/sdk - I'm not sure where the targets are actually located.

Reproduction Steps

dotnet new wasmconsole
dotnet publish -o "C:/publishLocation"

Expected behavior

The output written to "C:/publishLocation" is the published files for the project.

Actual behavior

The output written to "C:/publishLocation" does not contain all the files required to actually run the project.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

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