What's new in the SDK and tooling for .NET 10
This article describes new features and enhancements in the .NET SDK for .NET 10. It's updated for Preview 2.
New features and enhancements
Pruning of framework-provided package references
Starting in .NET 10, the NuGet Audit feature can now prune framework-provided package references that aren't used by the project. This feature is enabled by default for all net target frameworks (for example, net8.0 and net10.0) and .NET Standard 2.0 and greater target frameworks. This change helps reduce the number of packages that are restored and analyzed during the build process, which can lead to faster build times and reduced disk space usage. It also can lead to a reduction in false positives from NuGet Audit and other dependency-scanning mechanisms.
When this feature is enabled, you may see a reduction in the contents of your applications' generated .deps.json files. Any package references supplied by the .NET runtime are automatically removed from the generated dependency file.
While this feature is enabled by default for the listed TFMs, you can disable it by setting the RestoreEnablePackagePruning property to false in your project file or Directory.Build.props file.
More consistent command order
Starting in .NET 10, the dotnet CLI tool includes new aliases for common commands to make them easier to remember and type. The new commands are:
dotnet package adddotnet package listdotnet package removedotnet reference adddotnet reference listdotnet reference remove
These commands are aliases for the existing verb-first forms: dotnet add package, dotnet list package, dotnet remove package, dotnet add reference, dotnet list reference, and dotnet remove reference.
The new noun-first forms align with general CLI standards, making the dotnet CLI more consistent with other tools. While the verb-first forms continue to work, using the noun-first forms for improved readability and consistency in scripts and documentation is recommended.
