[automated] Update man pages (#50568)

marcpopMSFT · web-flow · commit c2811c136f95 · 2025-09-09T13:25:54.000-07:00
diff --git a/documentation/manpages/sdk/dotnet-nuget-locals.1 b/documentation/manpages/sdk/dotnet-nuget-locals.1
@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-nuget-locals" "1" "2025-06-13" "" ".NET Documentation"
+.TH "dotnet-nuget-locals" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet nuget locals
 .PP
@@ -42,7 +42,7 @@ The \f[V]dotnet nuget locals\f[R] command clears or lists local NuGet resources
 The cache location to list or clear.
 It accepts one of the following values:
 .IP \[bu] 2
-\f[V]all\f[R] - Indicates that the specified operation is applied to all cache types: http-request cache, global packages cache, and the temporary cache.
+\f[V]all\f[R] - Indicates that the specified operation is applied to all cache types: http-request cache, global packages cache, temporary cache, and plugins cache.
 .IP \[bu] 2
 \f[V]http-cache\f[R] - Indicates that the specified operation is applied only to the http-request cache.
 The other cache locations aren\[cq]t affected.
@@ -52,6 +52,9 @@ The other cache locations aren\[cq]t affected.
 .IP \[bu] 2
 \f[V]temp\f[R] - Indicates that the specified operation is applied only to the temporary cache.
 The other cache locations aren\[cq]t affected.
+.IP \[bu] 2
+\f[V]plugins-cache\f[R] - Indicates that the specified operation is applied only to the plugins cache.
+The other cache locations aren\[cq]t affected.
 .RE
 .SH OPTIONS
 .IP \[bu] 2
@@ -83,7 +86,7 @@ The list option is used to display the location of the specified cache type.
 .RE
 .SH EXAMPLES
 .IP \[bu] 2
-Displays the paths of all the local cache directories (http-cache directory, global-packages cache directory, and temporary cache directory):
+Displays the paths of all the local cache directories (http-cache directory, global-packages cache directory, temporary cache directory, and plugins cache directory):
 .RS 2
 .IP
 .nf
@@ -103,7 +106,17 @@ dotnet nuget locals http-cache --list
 .fi
 .RE
 .IP \[bu] 2
-Clears all files from all local cache directories (http-cache directory, global-packages cache directory, and temporary cache directory):
+Displays the path for the local plugins cache directory:
+.RS 2
+.IP
+.nf
+\f[C]
+dotnet nuget locals plugins-cache --list
+\f[R]
+.fi
+.RE
+.IP \[bu] 2
+Clears all files from all local cache directories (http-cache directory, global-packages cache directory, temporary cache directory, and plugins cache directory):
 .RS 2
 .IP
 .nf
@@ -132,6 +145,16 @@ dotnet nuget locals temp -c
 \f[R]
 .fi
 .RE
+.IP \[bu] 2
+Clears all files in local plugins cache directory:
+.RS 2
+.IP
+.nf
+\f[C]
+dotnet nuget locals plugins-cache -c
+\f[R]
+.fi
+.RE
 .SS Troubleshooting
 .PP
 For information on common problems and errors while using the \f[V]dotnet nuget locals\f[R] command, see Managing the NuGet cache.
diff --git a/documentation/manpages/sdk/dotnet-nuget-push.1 b/documentation/manpages/sdk/dotnet-nuget-push.1
@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-nuget-push" "1" "2025-06-13" "" ".NET Documentation"
+.TH "dotnet-nuget-push" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet nuget push
 .PP
@@ -26,7 +26,7 @@ dotnet-nuget-push - Pushes a package to the server and publishes it.
 .IP
 .nf
 \f[C]
-dotnet nuget push [<ROOT>] [-d|--disable-buffering] [--force-english-output]
+dotnet nuget push [<ROOT>] [--allow-insecure-connections] [-d|--disable-buffering] [--force-english-output]
     [--interactive] [-k|--api-key <API_KEY>] [-n|--no-symbols]
     [--no-service-endpoint] [-s|--source <SOURCE>] [--skip-duplicate]
     [-sk|--symbol-api-key <API_KEY>] [-ss|--symbol-source <SOURCE>]
@@ -73,6 +73,12 @@ Specifies the file path to the package to be pushed.
 .RE
 .SH OPTIONS
 .IP \[bu] 2
+\f[B]\f[VB]--allow-insecure-connections\f[B]\f[R]
+.RS 2
+.PP
+Allows pushing to HTTP sources (insecure).
+.RE
+.IP \[bu] 2
 \f[B]\f[VB]-d|--disable-buffering\f[B]\f[R]
 .RS 2
 .PP
diff --git a/documentation/manpages/sdk/dotnet-nuget-sign.1 b/documentation/manpages/sdk/dotnet-nuget-sign.1
@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-nuget-sign" "1" "2025-06-13" "" ".NET Documentation"
+.TH "dotnet-nuget-sign" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet nuget sign
 .PP
@@ -49,8 +49,8 @@ The \f[V]dotnet nuget sign\f[R] command signs all the packages matching the firs
 The certificate with the private key can be obtained from a file or from a certificate installed in a certificate store by providing a subject name or a SHA-1 fingerprint.
 .RS
 .PP
-This command requires a certificate root store that is valid for both code signing and timestamping.
-Also, this command may not be supported on some combinations of operating system and .NET SDK.
+This command requires a certificate root store that\[cq]s valid for both code signing and timestamping.
+Also, this command might not be supported on some combinations of operating system and .NET SDK.
 For more information, see NuGet signed package verification.
 .RE
 .SH ARGUMENTS
@@ -108,9 +108,11 @@ If there are multiple matching certificates in the result, or no matching certif
 Specifies the fingerprint of the certificate used to search a local certificate store for the certificate.
 .PP
 Starting with .NET 9, this option can be used to specify the SHA-1, SHA-256, SHA-384, or SHA-512 fingerprint of the certificate.
-However, a \f[V]NU3043\f[R] warning is raised when a SHA-1 certificate fingerprint is used because it is no longer considered secure.
+However, a \f[V]NU3043\f[R] warning is raised when a SHA-1 certificate fingerprint is used because it\[cq]s no longer considered secure.
+In .NET 10 and later versions, the warning is elevated to an error.
+Only SHA-2 family fingerprints (SHA-256, SHA-384, and SHA-512) are supported.
 .PP
-All the previous versions of the .NET SDK continue to accept only SHA-1 certificate fingerprint.
+All pre-.NET 9 versions of the .NET SDK continue to accept only SHA-1 certificate fingerprint.
 .RE
 .IP \[bu] 2
 \f[B]\f[VB]--certificate-password <PASSWORD>\f[B]\f[R]
@@ -196,12 +198,12 @@ dotnet nuget sign foo.nupkg --certificate-path cert.pfx --certificate-password p
 .fi
 .RE
 .IP \[bu] 2
-Sign \f[I]foo.nupkg\f[R] with certificate (password protected) matches with the specified SHA-1 fingerprint in the default certificate store (CurrentUser):
+Sign \f[I]foo.nupkg\f[R] with certificate (password protected) matches with the specified SHA-256 fingerprint in the default certificate store (CurrentUser):
 .RS 2
 .IP
 .nf
 \f[C]
-dotnet nuget sign foo.nupkg --certificate-fingerprint 89967D1DD995010B6C66AE24FF8E66885E6E03A8 --certificate-password password
+dotnet nuget sign foo.nupkg --certificate-fingerprint B2C40F2F8775D7B7EBEB76BD5A9D3A4BC3F4B8A4D8D7C5F8A4C6B3E7A9E2D5F1 --certificate-password password
 \f[R]
 .fi
 .RE
@@ -216,12 +218,12 @@ dotnet nuget sign foo.nupkg --certificate-subject-name \[dq]Test certificate for
 .fi
 .RE
 .IP \[bu] 2
-Sign \f[I]foo.nupkg\f[R] with certificate (password protected) matches with the specified SHA-1 fingerprint in the certificate store CurrentUser:
+Sign \f[I]foo.nupkg\f[R] with certificate (password protected) matches with the specified SHA-256 fingerprint in the certificate store CurrentUser:
 .RS 2
 .IP
 .nf
 \f[C]
-dotnet nuget sign foo.nupkg --certificate-fingerprint 89967D1DD995010B6C66AE24FF8E66885E6E03A8 --certificate-password password --certificate-store-location CurrentUser --certificate-store-name Root
+dotnet nuget sign foo.nupkg --certificate-fingerprint B2C40F2F8775D7B7EBEB76BD5A9D3A4BC3F4B8A4D8D7C5F8A4C6B3E7A9E2D5F1 --certificate-password password --certificate-store-location CurrentUser --certificate-store-name Root
 \f[R]
 .fi
 .RE
diff --git a/documentation/manpages/sdk/dotnet-publish.1 b/documentation/manpages/sdk/dotnet-publish.1
@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-publish" "1" "2025-06-13" "" ".NET Documentation"
+.TH "dotnet-publish" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet publish
 .PP
@@ -57,7 +57,7 @@ The application\[cq]s dependencies, which are copied from the NuGet cache into t
 The \f[V]dotnet publish\f[R] command\[cq]s output is ready for deployment to a hosting system (for example, a server, PC, Mac, laptop) for execution.
 It\[cq]s the only officially supported way to prepare the application for deployment.
 Depending on the type of deployment that the project specifies, the hosting system may or may not have the .NET shared runtime installed on it.
-For more information, see Publish .NET apps with the .NET CLI.
+For more information, see .NET application publishing overview.
 .SS Implicit restore
 .PP
 You don\[cq]t have to run \f[V]dotnet restore\f[R] because it\[cq]s run implicitly by all commands that require a restore to occur, such as \f[V]dotnet new\f[R], \f[V]dotnet build\f[R], \f[V]dotnet run\f[R], \f[V]dotnet test\f[R], \f[V]dotnet publish\f[R], and \f[V]dotnet pack\f[R].
@@ -346,7 +346,7 @@ Available since .NET 6.
 .PP
 Publishes the .NET runtime with your application so the runtime doesn\[cq]t need to be installed on the target machine.
 Default is \f[V]true\f[R] if a runtime identifier is specified and the project is an executable project (not a library project).
-For more information, see .NET application publishing and Publish .NET apps with the .NET CLI.
+For more information, see Self-contained deployment.
 .PP
 If this option is used without specifying \f[V]true\f[R] or \f[V]false\f[R], the default is \f[V]true\f[R].
 In that case, don\[cq]t put the solution or project argument immediately after \f[V]--self-contained\f[R], because \f[V]true\f[R] or \f[V]false\f[R] is expected in that position.
@@ -369,7 +369,7 @@ The URI of the NuGet package source to use during the restore operation.
 .PP
 Publishes the application for a given runtime.
 For a list of Runtime Identifiers (RIDs), see the RID catalog.
-For more information, see .NET application publishing and Publish .NET apps with the .NET CLI.
+For more information, see .NET application publishing overview.
 If you use this option, use \f[V]--self-contained\f[R] or \f[V]--no-self-contained\f[R] also.
 .RE
 .IP \[bu] 2
@@ -495,8 +495,6 @@ dotnet publish --no-dependencies
 .IP \[bu] 2
 \&.NET application publishing overview
 .IP \[bu] 2
-Publish .NET apps with the .NET CLI
-.IP \[bu] 2
 Target frameworks
 .IP \[bu] 2
 Runtime Identifier (RID) catalog
diff --git a/documentation/manpages/sdk/dotnet-reference-remove.1 b/documentation/manpages/sdk/dotnet-reference-remove.1
@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-reference-remove" "1" "2025-06-13" "" ".NET Documentation"
+.TH "dotnet-reference-remove" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet reference remove
 .PP
@@ -24,7 +24,7 @@
 dotnet-reference-remove - Removes project-to-project (P2P) references.
 .RS
 .PP
-If you\[cq]re using .NET 9 SDK or earlier, use the \[lq]verb first\[rq] form (dotnet-reference-remove) instead.
+If you\[cq]re using .NET 9 SDK or earlier, use the \[lq]verb first\[rq] form (dotnet-remove-reference) instead.
 The \[lq]noun first\[rq] form was introduced in .NET 10.
 For more information, see More consistent command order.
 .RE
diff --git a/documentation/manpages/sdk/dotnet-sln.1 b/documentation/manpages/sdk/dotnet-sln.1
@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-sln" "1" "2025-06-13" "" ".NET Documentation"
+.TH "dotnet-sln" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet sln
 .PP
@@ -39,29 +39,33 @@ The \f[V]dotnet sln\f[R] command provides a convenient way to list and modify pr
 To use the \f[V]dotnet sln\f[R] command, the solution file must already exist.
 If you need to create one, use the dotnet new command with the \f[V]sln\f[R] template name.
 .PP
-The following example creates a \f[I].sln\f[R] file in the current folder, with the same name as the folder:
+The following example creates an \f[I].slnx\f[R] file in the current folder, with the same name as the folder:
 .IP
 .nf
 \f[C]
 dotnet new sln
 \f[R]
 .fi
 .PP
-The following example creates a \f[I].sln\f[R] file in the current folder, with the specified file name:
+The following example creates an \f[I].slnx\f[R] file in the current folder, with the specified file name:
 .IP
 .nf
 \f[C]
 dotnet new sln --name MySolution
 \f[R]
 .fi
 .PP
-The following example creates a \f[I].sln\f[R] file in the specified folder, with the same name as the folder:
+The following example creates an \f[I].slnx\f[R] file in the specified folder, with the same name as the folder:
 .IP
 .nf
 \f[C]
 dotnet new sln --output MySolution
 \f[R]
 .fi
+.RS
+.PP
+In .NET 9 and earlier versions, \f[V]dotnet new sln\f[R] creates an \f[I].sln\f[R] file instead of an \f[I].slnx\f[R] file.
+.RE
 .SH ARGUMENTS
 .IP \[bu] 2
 \f[B]\f[VB]SOLUTION_FILE\f[B]\f[R]
diff --git a/documentation/manpages/sdk/dotnet-test.1 b/documentation/manpages/sdk/dotnet-test.1
@@ -15,7 +15,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-test" "1" "2025-06-13" "" ".NET Documentation"
+.TH "dotnet-test" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet test
 .SH NAME
@@ -736,7 +736,6 @@ Passing runsettings arguments through commandline (https://github.com/microsoft/
 dotnet test
     [--project <PROJECT_PATH>]
     [--solution <SOLUTION_PATH>]
-    [--directory <DIRECTORY_PATH>]
     [--test-modules <EXPRESSION>] 
     [--root-directory <ROOT_PATH>]
     [--max-parallel-test-modules <NUMBER>]
@@ -780,7 +779,7 @@ For information about how to manage NuGet feeds, see the \f[V]dotnet restore\f[R
 .SH OPTIONS
 .RS
 .PP
-You can use only one of the following options at a time: \f[V]--project\f[R], \f[V]--solution\f[R], \f[V]--directory\f[R], or \f[V]--test-modules\f[R].
+You can use only one of the following options at a time: \f[V]--project\f[R], \f[V]--solution\f[R], or \f[V]--test-modules\f[R].
 These options can\[cq]t be combined.
 In addition, when using \f[V]--test-modules\f[R], you can\[cq]t specify \f[V]--arch\f[R], \f[V]--configuration\f[R], \f[V]--framework\f[R], \f[V]--os\f[R], or \f[V]--runtime\f[R].
 These options are not relevant for an already-built module.
@@ -789,19 +788,15 @@ These options are not relevant for an already-built module.
 \f[B]\f[VB]--project <PROJECT_PATH>\f[B]\f[R]
 .RS 2
 .PP
-Specifies the path to the test project.
+Specifies the path of the project file to run (folder name or full path).
+If not specified, it defaults to the current directory.
 .RE
 .IP \[bu] 2
 \f[B]\f[VB]--solution <SOLUTION_PATH>\f[B]\f[R]
 .RS 2
 .PP
-Specifies the path to the solution.
-.RE
-.IP \[bu] 2
-\f[B]\f[VB]--directory <DIRECTORY_PATH>\f[B]\f[R]
-.RS 2
-.PP
-Specifies the path to a directory that contains a project or a solution.
+Specifies the path of the solution file to run (folder name or full path).
+If not specified, it defaults to the current directory.
 .RE
 .IP \[bu] 2
 \f[B]\f[VB]--test-modules <EXPRESSION>\f[B]\f[R]
@@ -993,16 +988,6 @@ dotnet test --solution ./TestProjects/TestProjects.sln
 .fi
 .RE
 .IP \[bu] 2
-Run the tests in a solution or project that can be found in the \f[V]TestProjects\f[R] directory:
-.RS 2
-.IP
-.nf
-\f[C]
-dotnet test --directory ./TestProjects
-\f[R]
-.fi
-.RE
-.IP \[bu] 2
 Run the tests using \f[V]TestProject.dll\f[R] assembly:
 .RS 2
 .IP
diff --git a/documentation/manpages/sdk/dotnet-tool-install.1 b/documentation/manpages/sdk/dotnet-tool-install.1
@@ -15,7 +15,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-tool-install" "1" "2025-07-30" "" ".NET Documentation"
+.TH "dotnet-tool-install" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet tool install
 .PP
@@ -65,6 +65,11 @@ To install a global tool in the default location, use the \f[V]--global\f[R] opt
 To install a global tool in a custom location, use the \f[V]--tool-path\f[R] option.
 .IP \[bu] 2
 To install a local tool, omit the \f[V]--global\f[R] and \f[V]--tool-path\f[R] options.
+.RS
+.PP
+[!WARNING] Make sure the directory you specify with the \f[V]--tool-path\f[R] option is secure.
+Tools installed in this location can be executed directly, so using an untrusted or shared path might introduce security risks.
+.RE
 .SS Installation locations
 .SS Global tools
 .PP
@@ -187,6 +192,14 @@ If one is found, create the manifest in that directory.
 If neither of the previous two steps finds a directory, create the manifest in the current working directory.
 .PP
 For more information on how manifests are located, see Install a local tool.
+.PP
+Starting in .NET 10, this flag is applied automatically if no tools manifest is found.
+.RS
+.PP
+[!WARNING] Don\[cq]t run tool commands from the \f[B]Downloads\f[R] folder or any shared location.
+The CLI walks up the directory tree to find a tool manifest, which might cause it to use a manifest you don\[cq]t expect.
+Always run tool commands from a trusted, project-specific directory.
+.RE
 .RE
 .IP \[bu] 2
 \f[B]\f[VB]--disable-parallel\f[B]\f[R]
