Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Epic]: Tooling support for central package management #9015

Open
4 of 8 tasks
cristinamanum opened this issue Jan 7, 2020 · 18 comments
Open
4 of 8 tasks

[Epic]: Tooling support for central package management #9015

cristinamanum opened this issue Jan 7, 2020 · 18 comments
Assignees
Labels
Area:RestoreCPM Central package management Epic Functionality:Restore Priority:2 Issues for the current backlog. Type:Feature

Comments

@cristinamanum
Copy link
Contributor

cristinamanum commented Jan 7, 2020

@cristinamanum cristinamanum self-assigned this Jan 7, 2020
@nkolev92 nkolev92 added the Area:RestoreCPM Central package management label Mar 31, 2020
@nkolev92 nkolev92 added Priority:2 Issues for the current backlog. Type:Feature labels Jul 16, 2020
@jeffkl jeffkl self-assigned this May 2, 2022
@jeffkl jeffkl changed the title [Centrally managing NuGet packages and versions] Visual Studio integration (MVP scenarios) [Feature]: Visual Studio integration when using central package management May 23, 2022
@jeffkl jeffkl changed the title [Feature]: Visual Studio integration when using central package management [Epic]: Visual Studio integration when using central package management May 23, 2022
@jeffkl jeffkl changed the title [Epic]: Visual Studio integration when using central package management [Epic]: Tooling support for central package management Aug 18, 2022
@andrew-hampton
Copy link

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

@jeffkl
Copy link
Contributor

jeffkl commented Sep 26, 2022

@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
Copy link

slang25 commented Feb 23, 2023

@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
Copy link
Contributor

jeffkl commented Feb 23, 2023

@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
Copy link
Contributor

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
Copy link

slang25 commented Feb 23, 2023

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

@slang25
Copy link

slang25 commented Feb 24, 2023

So that's 7.0.200

@martinrrm
Copy link
Contributor

Which VS version are you using?

@slang25
Copy link

slang25 commented Feb 25, 2023

This is on macOS using the sdk

@japj
Copy link

japj commented Apr 15, 2023

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
Copy link

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
Copy link

cremor commented Apr 17, 2023

@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
Copy link
Contributor

jebriede commented May 8, 2023

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

@jebriede
Copy link
Contributor

jebriede commented May 8, 2023

@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
Copy link

cremor commented May 9, 2023

  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
Copy link
Contributor

@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.

  1. 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
Copy link

cremor commented May 22, 2023

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
Copy link

IanKemp commented Jul 12, 2023

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

@martinrrm please can you do this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area:RestoreCPM Central package management Epic Functionality:Restore Priority:2 Issues for the current backlog. Type:Feature
Projects
None yet
Development

No branches or pull requests