Edit

Share via

PrunePackageReference marks direct prunable references with PrivateAssets=all and IncludeAssets=none

The PrunePackageReference feature automatically removes transitive packages that are provided by the target platform. With this change, the feature also marks directly prunable PackageReference items with PrivateAssets=all and IncludeAssets=none attributes. These attributes prevent the packages from appearing in generated dependency lists for packages.

Version introduced

.NET 10 Preview 7

Previous behavior

In earlier .NET 10 previews, directly prunable PackageReference items might have generated an NU1510 warning but still appeared in the generated .nuspec dependencies for all target frameworks, even those where the package is provided by the platform.

For example, consider a multi-targeting project with the following configuration:

<PropertyGroup>
  <TargetFramework>net9.0;net472</TargetFramework>
</PropertyGroup>

<ItemGroup>
  <PackageReference Include="System.Text.Json" Version="9.0.4" />
</ItemGroup>

Such a project file generated a .nuspec file with dependencies for both target frameworks:

<dependencies>
  <group targetFramework=".NETFramework4.7.2">
    <dependency id="System.Text.Json" version="9.0.4" />
  </group>
  <group targetFramework="net9.0">
    <dependency id="System.Text.Json" version="9.0.4" />
  </group>
</dependencies>

New behavior

Starting in .NET 10 Preview 7, directly prunable PackageReference items are automatically marked with PrivateAssets=all and IncludeAssets=none, which excludes them from the generated dependencies for target frameworks where they're provided by the platform.

The same project configuration now generates a .nuspec file with the prunable dependency removed from the target framework that provides it (.NET 9):

<dependencies>
  <group targetFramework=".NETFramework4.7.2">
    <dependency id="System.Text.Json" version="9.0.4" />
  </group>
  <group targetFramework="net9.0">
  </group>
</dependencies>

Type of breaking change

This is a behavioral change.

Reason for change

This change ensures that package dependencies accurately reflect the actual requirements for each target framework. It prevents unnecessary package references from appearing in generated packages when those APIs are already provided by the target framework.

  • If you create a package and get a NU1510 warning, follow the instructions there.
  • If you create a package and the generated .nuspec dependencies don't contain a referenced package for any target framework, remove the reference from the project file as it's not needed.
  • If the referenced package appears in the .nuspec file, no action is needed.

Affected APIs

None.

See also