[browser] Publish wasmbrowser app from Visual Studio doesn't respect "include RID in output path"

[maraf]

1. Install WebAssembly Browser App template via command: dotnet workload install wasm-experimental
2. Create a new WebAssembly Browser App via Visual studio.
3. Publish the project to folder.

Output is located in bin/Release/net8.0/publish instead of bin/Release/net8.0/browser-wasm/publish

The same setup works for blazorwasm template

[ghost]

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

Issue Details

---

1. Install WebAssembly Browser App template via command: dotnet workload install wasm-experimental
2. Create a new WebAssembly Browser App via Visual studio.
3. Publish the project to folder.

Output is located in bin/Release/net8.0/publish instead of bin/Release/net8.0/browser-wasm/publish

Author:	maraf
Assignees:	maraf
Labels:	arch-wasm, area-Build-mono, os-browser
Milestone:	9.0.0

[JakeYallop]

This might also be related to #94319

[maraf]

This might also be related to #94319

It is a different issue, because it uses completely different SDK under the hood (the plan is to migrate to the SDK used by wasmbrowser)

[maraf]

The issue is this workaround

runtime/src/mono/nuget/Microsoft.NET.Sdk.WebAssembly.Pack/build/Microsoft.NET.Sdk.WebAssembly.Browser.targets

Lines 198 to 199 in 43b55fa

	<!-- Workaround for https://github.com/dotnet/sdk/issues/12114-->
	<PublishDir Condition="'$(AppendRuntimeIdentifierToOutputPath)' != 'true' AND '$(PublishDir)' == '$(OutputPath)$(RuntimeIdentifier)\$(PublishDirName)\'">$(OutputPath)$(PublishDirName)\</PublishDir>

I'm not sure yet why I see it working for Blazor SDK correctly (maybe I oversaw it doesn't?)

The FolderPublish.pubxml is different

WasmBrowser

<?xml version="1.0" encoding="utf-8"?>
<!--
https://go.microsoft.com/fwlink/?LinkID=208121.
-->
<Project>
  <PropertyGroup>
    <Configuration>Release</Configuration>
    <Platform>Any CPU</Platform>
    <PublishDir>bin\Release\net9.0\browser-wasm\publish\</PublishDir>
    <PublishProtocol>FileSystem</PublishProtocol>
    <_TargetId>Folder</_TargetId>
  </PropertyGroup>
</Project>

Blazor

<?xml version="1.0" encoding="utf-8"?>
<!--
https://go.microsoft.com/fwlink/?LinkID=208121.
-->
<Project>
  <PropertyGroup>
    <DeleteExistingFiles>false</DeleteExistingFiles>
    <ExcludeApp_Data>false</ExcludeApp_Data>
    <LaunchSiteAfterPublish>true</LaunchSiteAfterPublish>
    <LastUsedBuildConfiguration>Release</LastUsedBuildConfiguration>
    <LastUsedPlatform>Any CPU</LastUsedPlatform>
    <PublishProvider>FileSystem</PublishProvider>
    <PublishUrl>bin\Release\net9.0\browser-wasm\publish\</PublishUrl>
    <WebPublishMethod>FileSystem</WebPublishMethod>
    <_TargetId>Folder</_TargetId>
  </PropertyGroup>
</Project>

Which might be related to project capabilities

[maraf]

In recent testing it seems that publish from VS dialog doesn't do publish at all. I'm seeing running a Build target.