[automated] Merge branch 'release/10.0.1xx' => 'main' (#50721)

Author: SimonZhao888

documentation/manpages/sdk/dotnet-nuget-locals.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-nuget-locals" "1" "2025-08-15" "" ".NET Documentation"
+.TH "dotnet-nuget-locals" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet nuget locals
 .PP

documentation/manpages/sdk/dotnet-nuget-push.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-nuget-push" "1" "2025-08-15" "" ".NET Documentation"
+.TH "dotnet-nuget-push" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet nuget push
 .PP

documentation/manpages/sdk/dotnet-nuget-sign.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-nuget-sign" "1" "2025-08-15" "" ".NET Documentation"
+.TH "dotnet-nuget-sign" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet nuget sign
 .PP

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

documentation/manpages/sdk/dotnet-reference-remove.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-reference-remove" "1" "2025-08-15" "" ".NET Documentation"
+.TH "dotnet-reference-remove" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet reference remove
 .PP

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]

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

documentation/manpages/sdk/dotnet-tool-install.1

@@ -15,7 +15,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-tool-install" "1" "2025-08-15" "" ".NET Documentation"
+.TH "dotnet-tool-install" "1" "2025-08-29" "" ".NET Documentation"
 .hy
 .SH dotnet tool install
 .PP

eng/pipelines/templates/jobs/sdk-build.yml

@@ -131,6 +131,7 @@ jobs:
         displayName: 🟣 Build
         env:
           BuildConfig: $(buildConfiguration)
+          OPENSSL_ENABLE_SHA1_SIGNATURES: 1
 
     ############### TESTING ###############
     - ${{ if eq(parameters.runTests, true) }}: