From 206efee1b1f102607bfdcec331c9bc2403d8bf96 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 19 May 2026 01:54:38 +0000 Subject: [PATCH 1/5] Document experimental C++ PackageReference support Agent-Logs-Url: https://github.com/NuGet/docs.microsoft.com-nuget/sessions/9a31d4d1-92c3-4fb6-aaba-1e7e752ca777 Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com> --- .../Package-References-in-Project-Files.md | 12 +++++++++--- .../install-use-packages-nuget-cli.md | 7 +++++-- .../migrate-packages-config-to-package-reference.md | 9 +++++++-- 3 files changed, 21 insertions(+), 7 deletions(-) diff --git a/docs/consume-packages/Package-References-in-Project-Files.md b/docs/consume-packages/Package-References-in-Project-Files.md index c7a6d1eca..b54de7b78 100644 --- a/docs/consume-packages/Package-References-in-Project-Files.md +++ b/docs/consume-packages/Package-References-in-Project-Files.md @@ -3,7 +3,7 @@ title: NuGet PackageReference in project files description: Details on NuGet PackageReference in project files as supported by NuGet 4.0+ and VS2017 and .NET Core 2.0 author: nkolev92 ms.author: nikolev -ms.date: 02/12/2026 +ms.date: 05/19/2026 ms.update-cycle: 1095-days ms.topic: concept-article --- @@ -16,9 +16,15 @@ With PackageReference, you can also use MSBuild conditions to choose package ref ## Project type support -By default, PackageReference is used for .NET projects, .NET Standard projects, and UWP projects targeting Windows 10 Build 15063 (Creators Update) and later, with the exception of C++ UWP projects. .NET Framework projects support PackageReference, but currently default to `packages.config`. To use PackageReference in a .NET Framework project, [migrate](../consume-packages/migrate-packages-config-to-package-reference.md) the dependencies from `packages.config` into your project file, then remove packages.config. +By default, PackageReference is used for .NET projects, .NET Standard projects, and UWP projects targeting Windows 10 Build 15063 (Creators Update) and later. +C++ PackageReference support is experimental. +For the latest C++ support details, see [NuGet PackageReference for C++ projects in Visual Studio](https://devblogs.microsoft.com/cppblog/nuget-packagereference-for-c-projects-in-visual-studio/). +.NET Framework projects support PackageReference, but currently default to `packages.config`. +To use PackageReference in a .NET Framework project, [migrate](../consume-packages/migrate-packages-config-to-package-reference.md) the dependencies from `packages.config` into your project file, then remove packages.config. -ASP.NET apps that target the full .NET Framework include only [limited support](https://github.com/NuGet/Home/issues/5877) for PackageReference. C++ and JavaScript project types are unsupported. +ASP.NET apps that target the full .NET Framework include only [limited support](https://github.com/NuGet/Home/issues/5877) for PackageReference. +C++ projects have experimental PackageReference support. +JavaScript project types are unsupported. ## Adding a PackageReference diff --git a/docs/consume-packages/install-use-packages-nuget-cli.md b/docs/consume-packages/install-use-packages-nuget-cli.md index e0fd321c2..a763d9da9 100644 --- a/docs/consume-packages/install-use-packages-nuget-cli.md +++ b/docs/consume-packages/install-use-packages-nuget-cli.md @@ -3,7 +3,7 @@ title: Manage NuGet Packages with the NuGet CLI description: Find out how to use the NuGet CLI, nuget.exe, to manage NuGet packages in non-SDK-style projects that use a packages.config file to list package references. author: mikejo5000 ms.author: mikejo -ms.date: 04/08/2026 +ms.date: 05/19/2026 ms.topic: how-to # customer intent: As a developer, I want to find out how to use the NuGet CLI so that I can manage NuGet packages in my projects and solutions. --- @@ -15,7 +15,10 @@ You can use the `nuget.exe` command-line interface (CLI) to manage NuGet package The NuGet CLI runs on .NET Framework and non-SDK-style projects, for example non-SDK-style projects that target .NET Standard libraries. The NuGet CLI commands can use a project [packages.config](../reference/packages-config.md) file that lists package references. For non-SDK-style projects that use `PackageReference` instead of *packages.config* for package references, use the [dotnet CLI](install-use-packages-dotnet-cli.md) instead. > [!NOTE] -> For most non-SDK-style projects that use *packages.config*, it's best to [migrate packages.config to `PackageReference`](migrate-packages-config-to-package-reference.md), and then use the dotnet CLI instead of the NuGet CLI to manage packages. However, you can't migrate C++ or ASP.NET projects. +> For most non-SDK-style projects that use *packages.config*, it's best to [migrate packages.config to `PackageReference`](migrate-packages-config-to-package-reference.md), and then use the dotnet CLI instead of the NuGet CLI to manage packages. +> However, you can't use the migration tool for C++ or ASP.NET projects. +> C++ PackageReference support is experimental. +> For the latest C++ support details, see [NuGet PackageReference for C++ projects in Visual Studio](https://devblogs.microsoft.com/cppblog/nuget-packagereference-for-c-projects-in-visual-studio/). For most commands, the NuGet CLI tool uses the current folder, unless you specify a different location in the command. To run NuGet CLI commands, open a command-line program and switch to the folder that contains your project file. diff --git a/docs/consume-packages/migrate-packages-config-to-package-reference.md b/docs/consume-packages/migrate-packages-config-to-package-reference.md index 1bb9a436f..8cd468c09 100644 --- a/docs/consume-packages/migrate-packages-config-to-package-reference.md +++ b/docs/consume-packages/migrate-packages-config-to-package-reference.md @@ -3,7 +3,7 @@ title: Migrating from packages.config to PackageReference formats description: Details on how to migrate a project from the packages.config management format to PackageReference as supported by NuGet 4.0+ and VS2017 and .NET Core 2.0 author: JonDouglas ms.author: jodou -ms.date: 08/23/2021 +ms.date: 05/19/2026 ms.topic: upgrade-and-migration-article --- @@ -23,6 +23,8 @@ Visual Studio 2017 Version 15.7 and later supports migrating a project from the * NuGet PackageReference is not available in Visual Studio 2015 and earlier. Migrated projects can be opened only in Visual Studio 2017 and later. * Migration is not currently available for C++ and ASP.NET projects. + C++ PackageReference support is experimental. + For the latest C++ support details, see [NuGet PackageReference for C++ projects in Visual Studio](https://devblogs.microsoft.com/cppblog/nuget-packagereference-for-c-projects-in-visual-studio/). * Some packages may not be fully compatible with PackageReference. For more information, see [package compatibility issues](#package-compatibility-issues). In addition, there are some differences in how PackageReferences work compared to packages.config. For example, [Constraints on upgrade versions](../consume-packages/reinstalling-and-updating-packages.md#constraints-on-upgrade-versions) is not supported by PackageReference, but PackageReference adds support for [Floating Versions](../consume-packages/package-references-in-project-files.md#floating-versions). @@ -43,7 +45,10 @@ Perform any one of the following NuGet actions: * Run NuGet restore - Right-click on the solution node in the Solution Explorer and select `Restore NuGet Packages` * Build the project which also triggers NuGet restore -You should now be able to see the migration option. Note that this option is not supported and will not show up for ASP.NET and C++ project types. +You should now be able to see the migration option. +Note that this option is not supported and won't show up for ASP.NET and C++ project types. +C++ PackageReference support is experimental. +For the latest C++ support details, see [NuGet PackageReference for C++ projects in Visual Studio](https://devblogs.microsoft.com/cppblog/nuget-packagereference-for-c-projects-in-visual-studio/). ## Migration steps From e1493a1b4925bf781d5f0096e5df87d5bcaadcef Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 19 May 2026 02:11:57 +0000 Subject: [PATCH 2/5] Remove duplicated C++ experimental support note Agent-Logs-Url: https://github.com/NuGet/docs.microsoft.com-nuget/sessions/e095afaa-0c6d-4443-ad08-03f27e620527 Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com> --- .../migrate-packages-config-to-package-reference.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/consume-packages/migrate-packages-config-to-package-reference.md b/docs/consume-packages/migrate-packages-config-to-package-reference.md index 8cd468c09..279909fd7 100644 --- a/docs/consume-packages/migrate-packages-config-to-package-reference.md +++ b/docs/consume-packages/migrate-packages-config-to-package-reference.md @@ -23,8 +23,6 @@ Visual Studio 2017 Version 15.7 and later supports migrating a project from the * NuGet PackageReference is not available in Visual Studio 2015 and earlier. Migrated projects can be opened only in Visual Studio 2017 and later. * Migration is not currently available for C++ and ASP.NET projects. - C++ PackageReference support is experimental. - For the latest C++ support details, see [NuGet PackageReference for C++ projects in Visual Studio](https://devblogs.microsoft.com/cppblog/nuget-packagereference-for-c-projects-in-visual-studio/). * Some packages may not be fully compatible with PackageReference. For more information, see [package compatibility issues](#package-compatibility-issues). In addition, there are some differences in how PackageReferences work compared to packages.config. For example, [Constraints on upgrade versions](../consume-packages/reinstalling-and-updating-packages.md#constraints-on-upgrade-versions) is not supported by PackageReference, but PackageReference adds support for [Floating Versions](../consume-packages/package-references-in-project-files.md#floating-versions). From b0e61f94e33d45b12bc1358446e4676fdcde7724 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 19 May 2026 02:12:36 +0000 Subject: [PATCH 3/5] Remove redundant C++ experimental support sentence Agent-Logs-Url: https://github.com/NuGet/docs.microsoft.com-nuget/sessions/e095afaa-0c6d-4443-ad08-03f27e620527 Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com> --- docs/consume-packages/Package-References-in-Project-Files.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/consume-packages/Package-References-in-Project-Files.md b/docs/consume-packages/Package-References-in-Project-Files.md index b54de7b78..079ba2253 100644 --- a/docs/consume-packages/Package-References-in-Project-Files.md +++ b/docs/consume-packages/Package-References-in-Project-Files.md @@ -23,7 +23,6 @@ For the latest C++ support details, see [NuGet PackageReference for C++ projects To use PackageReference in a .NET Framework project, [migrate](../consume-packages/migrate-packages-config-to-package-reference.md) the dependencies from `packages.config` into your project file, then remove packages.config. ASP.NET apps that target the full .NET Framework include only [limited support](https://github.com/NuGet/Home/issues/5877) for PackageReference. -C++ projects have experimental PackageReference support. JavaScript project types are unsupported. ## Adding a PackageReference From 9f7f701421b8f265a0a1c007415e17b174f2e2ac Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 19 May 2026 15:48:53 +0000 Subject: [PATCH 4/5] Reorder C++ support notes in project type support section Agent-Logs-Url: https://github.com/NuGet/docs.microsoft.com-nuget/sessions/94c7e872-4338-471a-8b63-3151d361d857 Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com> --- docs/consume-packages/Package-References-in-Project-Files.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/consume-packages/Package-References-in-Project-Files.md b/docs/consume-packages/Package-References-in-Project-Files.md index 079ba2253..4229831a8 100644 --- a/docs/consume-packages/Package-References-in-Project-Files.md +++ b/docs/consume-packages/Package-References-in-Project-Files.md @@ -17,11 +17,11 @@ With PackageReference, you can also use MSBuild conditions to choose package ref ## Project type support By default, PackageReference is used for .NET projects, .NET Standard projects, and UWP projects targeting Windows 10 Build 15063 (Creators Update) and later. -C++ PackageReference support is experimental. -For the latest C++ support details, see [NuGet PackageReference for C++ projects in Visual Studio](https://devblogs.microsoft.com/cppblog/nuget-packagereference-for-c-projects-in-visual-studio/). .NET Framework projects support PackageReference, but currently default to `packages.config`. To use PackageReference in a .NET Framework project, [migrate](../consume-packages/migrate-packages-config-to-package-reference.md) the dependencies from `packages.config` into your project file, then remove packages.config. +C++ PackageReference support is experimental. +For the latest C++ support details, see [NuGet PackageReference for C++ projects in Visual Studio](https://devblogs.microsoft.com/cppblog/nuget-packagereference-for-c-projects-in-visual-studio/). ASP.NET apps that target the full .NET Framework include only [limited support](https://github.com/NuGet/Home/issues/5877) for PackageReference. JavaScript project types are unsupported. From 45d1d13fee7915b383a9a2bf0c25a1a7c98a2bd5 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 19 May 2026 15:49:29 +0000 Subject: [PATCH 5/5] Add spacing between support paragraphs Agent-Logs-Url: https://github.com/NuGet/docs.microsoft.com-nuget/sessions/94c7e872-4338-471a-8b63-3151d361d857 Co-authored-by: nkolev92 <2878341+nkolev92@users.noreply.github.com> --- docs/consume-packages/Package-References-in-Project-Files.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/consume-packages/Package-References-in-Project-Files.md b/docs/consume-packages/Package-References-in-Project-Files.md index 4229831a8..6a7718a94 100644 --- a/docs/consume-packages/Package-References-in-Project-Files.md +++ b/docs/consume-packages/Package-References-in-Project-Files.md @@ -17,6 +17,7 @@ With PackageReference, you can also use MSBuild conditions to choose package ref ## Project type support By default, PackageReference is used for .NET projects, .NET Standard projects, and UWP projects targeting Windows 10 Build 15063 (Creators Update) and later. + .NET Framework projects support PackageReference, but currently default to `packages.config`. To use PackageReference in a .NET Framework project, [migrate](../consume-packages/migrate-packages-config-to-package-reference.md) the dependencies from `packages.config` into your project file, then remove packages.config.