dotnet publish multiple blazor webassembly apps generate invalid blazor.boot.json manifests

[javiercn]

• Create a hosted blazor webassembly app.
• Add a second app
• Configure the apps to be served from different subpaths (use https://github.com/javiercn/BlazorMultipleApps as a reference).
• Run dotnet publish on the server app
• Check the contents of the manifest and you'll see that the assemblies are not defined.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[pranavkm]

Here's a snippet you could use in an app targeting the 5.0.2 SDK to workaround this issue:

<Target Name="NoSoupForBlazorSdk" BeforeTargets="_ProcessPublishFilesForBlazor">
    <ItemGroup>
      <_BlazorPublishBootResource
        Include="@(ResolvedFileToPublish)"
        Condition="!$([System.String]::Copy('%(RelativePath)').Replace('/','\').StartsWith('wwwroot\_framework')) AND '%(Extension)' != '.a'" />
    </ItemGroup>
  </Target>