Skip to content

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

Open
5 of 6 issues completed
Open

Description

@cristinamanum

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

Issues

Pull Requests

Activity

  1. self-assigned this
    on Jan 7, 2020
  2. self-assigned this
    on May 2, 2022
  3. changed the title [-][Centrally managing NuGet packages and versions] Visual Studio integration (MVP scenarios)[/-] [+][Feature]: Visual Studio integration when using central package management[/+] on May 23, 2022
  4. changed the title [-][Feature]: Visual Studio integration when using central package management[/-] [+][Epic]: Visual Studio integration when using central package management[/+] on May 23, 2022
  5. changed the title [-][Epic]: Visual Studio integration when using central package management[/-] [+][Epic]: Tooling support for central package management[/+] on Aug 18, 2022
  6. andrew-hampton commented on Sep 22, 2022

    @andrew-hampton

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

  7. 14 remaining items

  8. cremor commented on May 9, 2023

    @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 Respect upper bounds of Version Range when updating in UI, PMC and dotnet package 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/sdk#48903
      Add support for batch "Add a reference to a project file" invocation #12629
  9. martinrrm commented on May 22, 2023

    @martinrrm
    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.
  10. cremor commented on May 22, 2023

    @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).
  11. IanKemp commented on Jul 12, 2023

    @IanKemp

    [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

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions