Blazor WASM app leaves untrimmed System.IO.Pipelines assembly by default #27782
Labels
affected-all
This issue impacts all the customers
area-blazor
Includes: Blazor, Razor Components
bug
This issue describes a behavior which is not expected - a bug.
feature-blazor-wasm
This issue is related to and / or impacts Blazor WebAssembly
severity-minor
This label is used by an internal tool
Milestone
Describe the bug
When publishing a default blazorwasm app,
System.IO.Pipelines.dll
is getting published to the output folder and is not trimmed at all.The reason this isn't trimmed by default is because
System.IO.Pipelines
isn't part of the shared fx / runtimepack in .NET Core. And the SDK only trims System assemblies that are in the runtimepack, and not assemblies that come as part of a NuGet package.We should be marking
System.IO.Pipelines.dll
as trimmable, so it gets trimmed when it isn't used.To Reproduce
dotnet new blazorwasm
dotnet publish -c Release
bin\Release\net5.0\publish\wwwroot\_framework\
See that System.IO.Pipelines.dll exists, and it doesn't have any IL trimmed from it.
Further technical details
dotnet --info
cc @pranavkm @SteveSandersonMS
The text was updated successfully, but these errors were encountered: