BlazorDebugProxy get copied as Content when using dotnet pack

[datvm]

Description

I am not sure why it's happening as I can't reproduce it with a new set of projects so I hope you can give me some pointers. I have two libraries projects (originally created as Blazor Web App): MyLib.Client and MyLib (which refers to MyLib.Client). My consuming projects will be Blazor Web Apps that use mostly static server-side rendering and some part are WebAssembly interactive.

• MyLib.Client contains components that should be available to the Blazor WebAssembly.
• MyLib contains some more components that are server rendered only.

Packing MyLib is fine, but I realized MyLib.Client was ~8MB, and unpacking the content, I found these files in the package's content folder (Texts is my own folder, the rest should not be there):

I realized it's from the bin\Release\net8.0\BlazorDebugProxy folder.

This is my .csproj files, Client first and server second:

<Project Sdk="Microsoft.NET.Sdk.Razor">

	<PropertyGroup>
		<!-- Nuget info -->
	</PropertyGroup>

	<PropertyGroup>
		<TargetFramework>net8.0</TargetFramework>
		<Nullable>enable</Nullable>
		<ImplicitUsings>enable</ImplicitUsings>
		<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
	</PropertyGroup>


	<ItemGroup>
		<SupportedPlatform Include="browser" />
	</ItemGroup>

	<ItemGroup>
		<PackageReference Include="BlazorMaterialWeb.Bundled" Version="2.1.0" />
		<PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="8.0.17" />
		<PackageReference Include="ServiceSharp" Version="2.1.0" />
	</ItemGroup>
</Project>

	<PropertyGroup>
		<!-- Nuget info -->
	</PropertyGroup>
	
	<PropertyGroup>
		<TargetFramework>net8.0</TargetFramework>
		<Nullable>enable</Nullable>
		<ImplicitUsings>enable</ImplicitUsings>
		<LangVersion>preview</LangVersion>
		<TreatWarningsAsErrors>true</TreatWarningsAsErrors>
		
		<NoWarn>NU5100</NoWarn> <!-- Nuget DLL -->
	</PropertyGroup>

	<ItemGroup>
		<FrameworkReference Include="Microsoft.AspNetCore.App" />

		<PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.Server" Version="8.0.17" />

		<PackageReference Include="Serilog.AspNetCore" Version="8.0.3" />
		<PackageReference Include="Serilog.Sinks.Seq" Version="9.0.0" />

		<PackageReference Include="BlazorMaterialWeb.Bundled" Version="2.1.0" />
		<PackageReference Include="ServiceSharp" Version="2.1.0" />
		<ProjectReference Include="..\ClientProject.csproj" />
	</ItemGroup>

Note: the <NoWarn>NU5100</NoWarn> <!-- Nuget DLL --> line is so that I can pack it due to it triggering only when running dotnet pack.

If I upload the Nuget package and use it anyway, when referring to the package, this happens:

Reproduction Steps

N/A

Expected behavior

The DLLs should not be copied.

Actual behavior

Extra DLLs from BlazorDebugProxy copied.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

[MihuBot]

I'm a bot. Here are possible related and/or duplicate issues (I may be wrong):

• Get rid of BlazorDebugProxy in release builds #25102
• BlazorDebugProxy in published out #25497

[javiercn]

@datvm thanks for contacting us.

Why are you referencing webassembly.server from a class library in the first place?

[javiercn]

Does using ExcludeAssets help you get rid of it?

https://learn.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files#controlling-dependency-assets

If none of this works, ultimately find the Content items and mark them as Pack=false.

We don't expect this package to be used for anything else other than the final web app and not in the context of packing, so our recommendation is, first to remove it from the RCL, second to account in your pack build for the files and remove them manually.

[datvm]

Thank you for pointing it out! Indeed that was the problem I think.

I do need that package reference because in my library there are calls to AddInteractiveWebAssemblyComponents and AddInteractiveWebAssemblyRenderMode which does not work without that package. It's intended to make our end projects shorter and simply call something like Library.BuildHostAsync().

Strangely, even when I put either-or-both Private and PrivateAssets like below, the files are still copied (and Nuget issue warning if not suppressed):

<PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.Server" Version="8.0.17" Private="false" PrivateAssets="All" />

If there is no better workaround, I will probably remove the package and put the calls in interfaces so only the end project will call it.

[javiercn]

@datvm thanks for the additional details.

I imagine is because the contents are custom packed. In general, is what I said, those are the debugger bits and we don't expect libraries to reference that package.

We are not planning to do anything to address this in the current or upcoming versions since it doesn't functionally impact apps, and there are MSBuild options to remove the contents in consuming apps.

The plan for 11.0 is likely to get rid of the debugger proxy from that package, since now the IDEs take care of launching it directly.