Skip to content

Support SDK Version Management #13127

Open

Description

@dansiegel

NuGet Product(s) Involved

NuGet.exe, Visual Studio Package Management UI

The Elevator Pitch

Project SDK's sometimes ship in the form of a NuGet. Some common examples:

The problem with this is that it isn't very well integrated into the NuGet dependency toolchain. For example if I am using the Microsoft.Build.NoTargets Sdk I might use:

<Project Sdk="Microsoft.Build.NoTargets/3.7.0">

Or I might version this through a global.json like:

{
  "msbuild-sdks": {
    "Microsoft.Build.NoTargets": "3.7.0"
  }
}

However since there is no tooling support when updates like version 3.7.56 become available I have no way of knowing that there is an update.

Additional Context and Details

No response

Activity

  1. baronfel commented on Jan 4, 2024

    @baronfel

    Having an official mechanism for this could also help the build of DotNet itself - currently when doing a full product build we build some SDKs and then have to change these files' content to use the newly built versions.

  2. added
    Priority:3Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog.
    on Jan 8, 2024
  3. 5 remaining items

  4. added
    Priority:3Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog.
    and removed
    Priority:3Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog.
    on Apr 29, 2024
  5. added
    Priority:3Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog.
    and removed
    Priority:3Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog.
    on Jun 27, 2024
  6. hakenr commented on Oct 19, 2024

    @hakenr

    This is a major issue that has made us reconsider using MSTest.Sdk. The behavior of NuGet Package Manager in Visual Studio makes it unusable, both for versioning within individual project files and for versioning within global.json (along with Central Package Management in Directory.Packages.props).

  7. added
    Priority:2Issues for the current backlog.
    Product:MSBuildSDKResolverThe NuGet powered SDK resolver. Owned by MSBuild team
    and removed
    Priority:3Issues under consideration. With enough upvotes, will be reconsidered to be added to the backlog.
    on Oct 28, 2024
  8. azchohfi commented on Oct 8, 2025

    @azchohfi

    Has there been any progress in this? I see this as a P2, but it invalidates a whole class of usage of NuGet packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions