NuGet 5.9 Release Notes

NuGet distribution vehicles:

¹ Installed with Visual Studio 2019 with .NET Core workload

Summary: What's New in 5.9.3

• [Security]: Microsoft Security Advisory CVE-2022-41032 | .NET Elevation of Privilege Vulnerability - #12149

Summary: What's New in 5.9.2

• [Security]: Microsoft Security Advisory CVE-2022-30184 | .NET Information Disclosure Vulnerability - #11883

Summary: What's New in 5.9

• Add "Update" context menu item for package dependencies that launches Package Manager UI with preselected packages to update - #10378

  

• Show the requested version (including floating version or version range request) in the "Version" column of the project list in the solution level Package Manager UI - #9827

  

• IntelliCode package suggestions in the Package Manager UI Browse tab released as an A/B test - #10053

• Extend the .nupkg.metadata file to include the installation source - #10354

• Introduce a new msbuild property to exclude build output for specific TFMs during pack task - #10396

Issues fixed in this release

DCRs(Design Change Request):

• The down icon icon when the latest package version is installed is not intuitive. The old green tick was perfect - #9789

• Nuget Debug verbosity should say where a package came from - #3055

• NuGet pack should catch incorrect omitting of the dot in version numbers - #9215

• [CPVM] Disable pinning of the central transitive dependencies - #10132

• net5 TFM: produce error when missing TPV - #9441

• Log package contenthash during restore logging (during extraction) - #10384

• Implement a pre-registration mechanism for legacy PR projects that call restore at solution open - #9986

• NuGet package recommender should work when more than one source is selected in package manager - #10433

• When restoring at normal verbosity, log which source a package is being restored from - #10461

Bugs:

• INuGetPackageFileService - Fetch Images and embedded licenses for Codespaces-connected and standalone - #10151

• VS OE: IProjectMetadataContextInfo missing formatter - #10079

• [CPVM-Perf] Reduce the information written to centralTransitiveDependencyGroups - #10002

• Restore operations that throw due to a project not being loaded are reported as NoOp in telemetry - #9985

• Icons with certain color pallets causes PM UI to crash VS - #10037

• [CPVM-Perf] Reduce the PackageSpec clone when adding the CPVM information - #10003

• PM UI - asyncify icon loading - #10009

• UI delay when loading icon URLs in PM UI - #8505

• Thread affinity in BitmapSource and WPF UI threads - #9161

• Warning for warning NU5128 when packastool with targetframework alias - #10097

• OutputPath logic in Pack targets in a customized build doesn't work properly - #9234

• VS OE: cache IServiceBroker instance on client - #10141

• Make creating NuGetProjectActions for uninstall from PM UI a parallel operation - #9956

• Performance: Reduce UIDelays in GetPackageSpecsAsync for Legacy projects and non PR projects - #9953

• dotnet nuget push *.nupkg doesn't push more than one file - #4393

• Output is wrapped at 80 characters on macOS when redirected - #10198

• Restore fails with -Source <Relative Path> - #9406

• netcoreapp5.0-windows does not round trip and does not parse platform information - #10177

• Custom CPS projects require AssemblyReferences project capability in order to restore. - #8071

• License and icon file existence check should always use a case-sensitive comparison - #9817

• DotnetCLiToolReference restores make it difficult to reason about no-op projects count/uptodateprojectscount - #10038

• Hard to see the dash-line box of package format when navigating by tab through the “Choose NuGet Package Manager Format” dialog in Dark theme - #9729

• Exclude transitive framework references from CollectFrameworkReferences - #10314

• Comparer static properties should be idempotent - #10339

• resolve internal contracts assembly loading (fix RPS or get exception) - #9919

• Replace GetService with GetServiceAsync in NuGet.Clients, Part 1 - #10362

• CLI installs should not install unlisted packages - #7466

• Static msbuild graph restore - unnnecessary logging about MSBuildStartupDirectory - #10335

• Project Dependencies of ProjectReferences marked as PrivateAssets should not be included in the lock file up to date check - #8565

• SDK projects with bad data not showing restore errors in VS - #10406

• NU1004 when restoring a solution that has mixed Legacy and netstandard2 projects from cmd line with LockedMode - #9623

• Pack includes content brought in through dependency packages into the current project's package (SDK based projects only) - #8867

• Add telemetry for NuGet's VS extensibility API faults - #10062

• Add GenerateRestoreGraphFile in static graph restore to improve debugability. - #10365

• Cannot open the NuGet Package manager - #10336

• NVDA/Narrator is not reading "License" label for "Apache-2.0" link - #10425

• The up to date status bar message is not great in VS - #9402

• packages.config package.lock.json uses an incorrect target framework - #10257

• Codespaces: fix telemetry from https://github.com/NuGet/NuGet.Client/pull/3786 - #10439

• Error NU1004 disappears when building solution after enabling “RestoreLockedMode” - #8973

• Tabbing through PMUI in the reverse should mirror forward direction - #10234

• Debugging PMUI in Experimental Instance sometimes throws InvalidCastException from SolutionView to ProjectView - #10416

• The default version is null after clicking a deprecated package in Browse tab - #10380

• The NuGet manager in Visual Studio reloads when focus is regained - #4176

• Remove IPackageSourceProvider2 and related types - #10098

• Package 'NameOfPackage' is incompatible with 'all' frameworks in project - #5127

• CreateVersionsAsync does unnecessary NuGetVersion Compares - #10436

• NuGet.Client should replace using of ManagedImageMonikers with KnownMonikers - #9977

• The deprecated icon overlaps with the version of the deprecated package in Browse tab - #10452

• PackageReference NU1604 error handling is different across VS and command line (Restore & Package Manager UI) - #9289

• Codespaces: necessary formatters not registered - #10467

• Remove net45 as as a target framework from NuGet.Frameworks - #10470

• Implementation - Add new telemetries to track events related to PMC and Powershell usage. - #10142

• Only one package shows in the Preview Changes window when there are multiple packages available to update in the Package Manager UI - #10483

• Empty frameworkReferences groups should be generated when packing multitargeted projects - #10218

• Hard to see the check-box of package in ‘Updates’ Tab is focused with a dash-line box when navigating through Tab in Blue/Blue (Extra Contrast)/Light themes - #8963

• Updates Tab checkboxes do not work well with screen-readers - #10449

• Updating in PMUI causes Object reference not set to an instance of an object - #9882

• Implementation - Add new telemetries to track events related to PMC and Powershell usage follow up. - #10478

• Copy-paste error in V2FeedPackageInfo - #10480

• NuGetPackageFileService fix - use using for disposable memorystream - #10503

List of all issues fixed in this release - 5.9.0

List of commits in this release - 5.9.0

Community contributions

Thank you to all the contributors who helped make this NuGet release awesome!

Summary: What's New in 5.9.1

• "dotnet nuget remove source nuget.org" doesn't work the first time - #10745
• Make default validation disabled on Linux, but enabled by default on Windows - #10713

List of all issues fixed in this release - 5.9.1

List of commits in this release - 5.9.1

Known issues

nuget 5.9 pack raises Null Reference exception. - #10685

Issue

When tring to pack using a .nuspec file, NuGet 5.9 version raises a null reference exception if explicit assembly references are specified without adding any reference groups for projects that target multiple frameworks.

Workaround

Use nuget.exe 5.8.1 or latest version other than 5.9.1.

Feedback welcome

Your feedback is important to us. If there are any problems with this release, check our GitHub Issues and Visual Studio Developer Community for existing issues. For new issues within NuGet, please report a GitHub Issue. For general NuGet experience issues, let us know via the Report a Problem option found in your favorite IDE under Help > Report a Problem.