[Blazor] Blazor single project experience follow ups

[javiercn]

We already checked-in initial support for the single project experience in the SDK. Based on exploratory testing with the template, we've discovered a set of issues we need to address to get into a functional template:

• [x] Fix service worker being incorrectly included. https://github.com/dotnet/aspnetcore/pull/49076
• [ ] Set StaticWebAssetBasePath unconditionally to / in multi-targeting builds on the .NET 8.0 project. https://github.com/dotnet/sdk/pull/33649
• [ ] Put the embedded configuration rule in the web SDK https://github.com/dotnet/sdk/pull/33649

  <ItemGroup>
    <StaticWebAssetsEmbeddedConfiguration
      Include="$(TargetFramework)"
      Condition="'$([MSBuild]::GetTargetPlatformIdentifier($(TargetFramework)))' == '' And $([MSBuild]::VersionGreaterThanOrEquals(8.0, $([MSBuild]::GetTargetFrameworkVersion($(TargetFramework)))))">
      <Platform>browser</Platform>
    </StaticWebAssetsEmbeddedConfiguration>
  </ItemGroup>

• [ ] Adjust the conventions on the targets. Fix similar conventions for content https://github.com/dotnet/sdk/pull/33649

  <ItemGroup Condition="'$([MSBuild]::GetTargetPlatformIdentifier($(TargetFramework)))' != 'browser'">
   <Compile Remove="**\**\*.Browser.cs" />
   <Compile Remove="**\Browser\**\*.cs" />
  </ItemGroup>
  
  <ItemGroup Condition="'$([MSBuild]::GetTargetPlatformIdentifier($(TargetFramework)))' != ''">
   <Compile Remove="**\**\*.Server.cs" />
   <Compile Remove="**\Server\**\*.cs" />
  </ItemGroup>

• [ ] Resolve conflicts on the template
  • App styles bundle. Covered as part of https://github.com/dotnet/aspnetcore/issues/47885
  • Configuration files. We need to update the Wasm SDK to provide a AssetMergeBehavior
• [ ] Get rid of the loading UI https://github.com/dotnet/aspnetcore/issues/49056

[SteveSandersonMS]

Also: Razor tooling behaves unpredictably when multitargeting and misses completions

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[kevin-weir]

This feature was mentioned a year ago by Dan Roth in the following presentation: https://youtu.be/0MBeYc9qcWY?t=650

Is there some technical reason/hurdle why this can't be delivered? It would certainly streamline Blazor development and reduce the learning curve of targeting both the client and server within the same app.