Trim dotnet-watch and Microsoft.AspNetCore.Components.WebAssembly.DevServer package content

[dougbu]

The following image shows the content of the 5.0.0-rtm.20479.12 version of the Microsoft.AspNetCore.Components.WebAssembly.DevServer package. This includes shared framework assemblies such as Microsoft.Extensions.Configuration.Abstractions.dll. They're present because they're brought in transitively though Microsoft.AspNetCore.Components.WebAssembly.Server and published along with the content we really want.

Bottom line here is #24816 changes to Microsoft.AspNetCore.Components.WebAssembly.DevServer.csproj didn't have the expected outcome. Further I need to revert those changes in #24983 because they cause conflicts between 5.0 AspNetCore assemblies in the SDK and 6.0 assemblies Microsoft.AspNetCore.Components.WebAssembly.Server.csproj references. Need another way to either clean up the publish content or limit what ends up in the DevServer package.

Options include at least:

1. List the exact files needed in the package in Microsoft.AspNetCore.Components.WebAssembly.DevServer.nuspec
2. Muck w/ an item group like @(ReferenceCopyLocalPaths) to remove all @(ExternalAspNetCoreAppReference) items as well as aspnetcorev2_inprocess.dll in a well-timed target

[dougbu]

Side note: @pranavkm and I have an open question about whether the package content is a bug worth fixing for 5.0.0 GA.

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.

[TanayParikh]

@dougbu is this still an issue?