[Epic]: Tooling support for central package management

[cristinamanum]

This is a tracking epic for work related to updating tooling to work with central package management (dotnet CLI, VS)

Issues

• [Feature]: Add support for central package management to dotnet add package #9022
• [Feature]: Add support for central package management to Visual Studio Package Manager UI for legacy projects #9521
• [Feature]: Add support for central package management to Visual Studio Package Manager UI for SDK-style projects #9018
• [Feature]: Add support for central package management to dotnet remove package #9023
• [Feature]: Add support for central package management to dotnet prune #9024
• [Bug]: NuGet Package Manager does not update Directory.Packages.props #11826

Pull Requests

• Support for dotnet add package command for CPM projects NuGet.Client#4792
• Dotnet add package support cpm NuGet.Client#4986

[andrew-hampton]

@jeffkl is there a target release for these tooling updates?

[jeffkl]

@jeffkl is there a target release for these tooling updates?

@andrew-hampton yes, the next release of Visual Studio 2022 should have the changes. For the .NET SDK, it will most likely be available with the first minor release of .NET 7.

[slang25]

@jeffkl I'm confused, I was expecting the latest 7.0.200 SDK to have dotnet add support, how can I track when that will ship?

[jeffkl]

@slang25 I thought it would be in Visual Studio 17.5 / .NET SDK 7.0.200. @martinrrm did the change not make the cut for 17.5?

[martinrrm]

Yes it was added in 17.5, and I'm able to use it in 7.0.200-preview.22628.1 . @slang25 which version of SDK are you using?

[slang25]

Thanks, this is what I'm seeing at the moment, I've only tried it on a few apps:

[slang25]

So that's 7.0.200

[martinrrm]

Which VS version are you using?

[slang25]

This is on macOS using the sdk

[japj]

Hi, are there any updates for VS package manager ui support for central package management?
(are you targeting a specific VS update for this?)

I have several colleagues at work that are wondering about this, since it has now been a year since Directory.Packages.props was introduced with nuget 6.2 (VS 17.2)

[tompazourek]

Hi, are there any updates for VS package manager ui support for central package management? (are you targeting a specific VS update for this?)

I have several colleagues at work that are wondering about this, since it has now been a year since Directory.Packages.props was introduced with nuget 6.2 (VS 17.2)

AFAIK, support was already implemented. Read here: https://devblogs.microsoft.com/nuget/announcing-nuget-6-5-the-sweetest-way-to-manage-your-packages/#streamlined-package-management-inside-visual-studio-with-directory-packages-props-support

[cremor]

@tompazourek But the first post in this issue contains links to multiple open issues related to VS package manger UI.

I've tried it myself and while it works sometimes, there are definitely still problems with it.

[jebriede]

[Team Triage]: @martinrrm can you the status of the issues listed in this epic? Thanks!

[jebriede]

@cremor please feel free to open an issue in GitHub with repro details for any issues you find with tooling support for CPM. Thanks!

[cremor]

1. Sometimes after updating packages via the Visual Studio NuGet UI my Directory.Packages.props file will not contain updated version numbers in the relevant <PackageVersion> lines, but instead contain new <PackageVersion Update...> lines. I don't know yet how to reproduce this bug. I'll create an issue once I know.
2. Updating a package with a version range in Directory.Packages.props overwrites the version range with the specific new version. This is point 2 of Version Range support in UI and PMC update #6566, so this also affects CPM.
3. Add support for easier CentralPackageManagement options dotnet/templating#6187
   Templates create compile errors in solutions with Central Package Management (CPM) dotnet/aspnetcore#48569
   Templates create compile errors in solutions with Central Package Management (CPM) dotnet/test-templates#300
   Add support for batch "Add a reference to a project file" invocation #12629

[martinrrm]

@cremor 1. I saw that behavior in the past one time and wasn't able to repro it since, I'll test it again but not sure what can cause that bug.

2. Are you updating using the PM UI? Support for floating versions and ranges is not available at the moment and should be disabled in the PM UI.

[cremor]

About point 2:

• Directory.Packages.props contains a version range like Version="[1.0.0, 2.0.0)".
• Package versions 1.0.0, 1.1.0 and 2.0.0 are available on the source.
• I open the NuGet Package Management UI in Visual Studio.
• The PM UI shows version 2.0.0 as an update (bad - or at least confusing).
• Actually doing the update via the PM UI only updates to 1.1.0 (good).
  I don't see anything "disabled in the PM UI" here.
• When doing the update via the PM UI, it overwrites the version in the Directory.Packages.props file to 1.1.0 (bad - upper bound is gone).
• If I would update in the PM UI again it would now update to version 2.0.0 (bad).

[IanKemp]

[Team Triage]: @martinrrm can you the status of the issues listed in this epic? Thanks!

@martinrrm please can you do this?