Update info on packing legacy csproj (#3481)

Author: zivkan

docs/consume-packages/migrate-packages-config-to-package-reference.md

@@ -87,7 +87,9 @@ You should now be able to see the migration option. Note that this option is not
 
 ## Create a package after migration
 
-Once the migration is complete, we recommend that you add a reference to the [nuget.build.tasks.pack](https://www.nuget.org/packages/nuget.build.tasks.pack) nuget package, and then use [msbuild -t:pack](../reference/msbuild-targets.md#pack-target) to create the package. Although in some scenarios you could use `dotnet.exe pack` instead of `msbuild -t:pack`, it is not recommended.
+Once the migration is complete, we recommend that you copy your package metadata from a `.nuspec` file to [MSBuild properties](../reference/msbuild-targets.md#pack-target), and then you can use `msbuild -t:pack` to create the package.
+If you are using Visual Studio 2022 or earlier, you will also need to install the NuGet.Build.Tasks.Pack package.
+From Visual Studio 2026, pack is built into MSBuild.
 
 ## Package compatibility issues
 

docs/create-packages/creating-a-package-msbuild.md

@@ -13,9 +13,12 @@ When you create a NuGet package from your code, you package that functionality i
 
 For .NET Core and .NET Standard projects that use the [SDK-style format](../resources/check-project-format.md), and any other SDK-style projects, NuGet uses information in the project file directly to create a package.  For a non-SDK-style project that uses `<PackageReference>`, NuGet also uses the project file to create a package.
 
-SDK-style projects have the pack functionality available by default. For non SDK-style PackageReference projects, you need to add the NuGet.Build.Tasks.Pack package to the project dependencies. For detailed information about MSBuild pack targets, see [NuGet pack and restore as MSBuild targets](../reference/msbuild-targets.md).
+SDK-style projects have the pack functionality available by default.
+For non-SDK-style PackageReference projects, it is also available by default starting from Visual Studio 2026.
+In earlier versions of Visual Studio you need to add the NuGet.Build.Tasks.Pack package to the project dependencies and we recommend removing this package reference when upgrading to Visual Studio 2026.
+For detailed information about MSBuild pack targets, see [NuGet pack and restore as MSBuild targets](../reference/msbuild-targets.md).
 
-The command that creates a package, `msbuild -t:pack`, is functionally equivalent to `dotnet pack`.
+For SDK-style projects, `msbuild -t:pack` is functionally equivalent to `dotnet pack`.
 
 > [!IMPORTANT]
 > This topic applies to [SDK-style](../resources/check-project-format.md) projects, typically .NET Core and .NET Standard projects, and to non-SDK-style projects that use PackageReference.
@@ -77,16 +80,33 @@ For details on declaring dependencies and specifying version numbers, see [Packa
 
 [!INCLUDE [choose-package-id](includes/choose-package-id.md)]
 
-## Add the NuGet.Build.Tasks.Pack package
+## Configure project for pack
 
-If you are using MSBuild with a non-SDK-style project and PackageReference, add the NuGet.Build.Tasks.Pack package to your project.
+SDK-style projects do not require any additional configuration.
 
-1. Open the project file and add the following after the `<PropertyGroup>` element:
+Non-SDK-style projects either need at least one package installed (via PackageReference, not packages.config), or the project explicitly needs to instruct NuGet to treat the project as a PackageReference project via the `RestoreProjectStyle` property.
+
+Visual Studio 2022 and earlier does not have pack built-in, so you also need to install the NuGet.Build.Tasks.Pack package.
+When upgrading to Visual Studio 2026 or later, we recommend uninstalling the package, so that you benefit from new features and bug fixes.
+
+1. Edit the project file.
+
+   If you want to explicitly instruct NuGet to treat the project as PackageReference (the project does not have any packages installed), find or add a `<PropertyGroup>` that does not have any `Condition` statement, and add:
+
+   ```xml
+   <PropertyGroup>
+     <!-- other properties -->
+     <RestoreProjectStyle>PackageReference</RestoreProjectStyle>
+     <!-- more properties are allowed -->
+   </PropertyGroup>
+   ```
+
+   If you are using Visual Studio 2022 or earlier, add the following after the `<PropertyGroup>` element:
 
    ```xml
    <ItemGroup>
      <!-- ... -->
-     <PackageReference Include="NuGet.Build.Tasks.Pack" Version="6.7.0" PrivateAssets="all" />
+     <PackageReference Include="NuGet.Build.Tasks.Pack" Version="6.14.0" PrivateAssets="all" />
      <!-- ... -->
    </ItemGroup>
    ```
@@ -98,7 +118,7 @@ If you are using MSBuild with a non-SDK-style project and PackageReference, add
 
    You typically want to start the Developer Command Prompt for Visual Studio from the **Start** menu, as it will be configured with all the necessary paths for MSBuild.
 
-3. Switch to the folder containing the project file and type the following command to install the NuGet.Build.Tasks.Pack package.
+3. Switch to the folder containing the project file and type the following command to restore the NuGet.Build.Tasks.Pack package.
 
    ```cmd
    # Uses the project file in the current folder by default

docs/reference/msbuild-targets.md

@@ -38,6 +38,9 @@ Similarly, you can write an MSBuild task, write your own target and consume NuGe
 
 For .NET projects that use the `PackageReference` format, using `msbuild -t:pack` draws inputs from the project file to use in creating a NuGet package.
 
+Non-SDK-style projects will need to install the NuGet.Build.Tasks.Pack package when using Visual Studio 2022 or earlier.
+We recommend uninstalling this package when upgrading to Visual Studio 2026 to ensure your project can use the latest pack features and bug fixes.
+
 The following table describes the MSBuild properties that can be added to a project file within the first `<PropertyGroup>` node. You can make these edits easily in Visual Studio 2017 and later by right-clicking the project and selecting **Edit {project_name}** on the context menu. For convenience, the table is organized by the equivalent property in a [`.nuspec` file](../reference/nuspec.md).
 
 > [!NOTE]
@@ -307,7 +310,8 @@ When using `MSBuild -t:pack -p:IsTool=true`, all output files, as specified in t
 
 ### Packing using a `.nuspec` file
 
-Although it is recommended that you [include all the properties](../reference/msbuild-targets.md#pack-target) that are usually in the `.nuspec` file in the project file instead, you can choose to use a `.nuspec` file to pack your project. For a non-SDK-style project that uses `PackageReference`, you must import `NuGet.Build.Tasks.Pack.targets` so that the pack task can be executed. You still need to restore the project before you can pack a nuspec file. (An SDK-style project includes the pack targets by default.)
+Although it is recommended that you [include all the properties](../reference/msbuild-targets.md#pack-target) that are usually in the `.nuspec` file in the project file instead, you can choose to use a `.nuspec` file to pack your project.
+You still need to restore the project before you can pack a nuspec file. (An SDK-style project includes the pack targets by default.)
 
 The target framework of the project file is irrelevant and not used when packing a nuspec. The following three MSBuild properties are relevant to packing using a `.nuspec`: