Merge branch 'main' into nagilson-create-tool-manifest-by-default

Author: nagilson

documentation/manpages/sdk/dotnet-build-server.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-build-server" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-build-server" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet build-server
 .PP

documentation/manpages/sdk/dotnet-build.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-build" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-build" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet build
 .PP

documentation/manpages/sdk/dotnet-clean.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-clean" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-clean" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet clean
 .PP

documentation/manpages/sdk/dotnet-dev-certs.1

@@ -15,7 +15,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-dev-certs" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-dev-certs" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet dev-certs
 .PP
@@ -119,6 +119,7 @@ successfully removed from the machine.
 .PP
 Exports the certificate to a file so that it can be used by other tools.
 Specify the full path to the exported certificate file, including the file name.
+The containing directories must already exist and access to them should be restricted.
 The type of certificate files that are created depends on which options are used with \f[V]--export-path\f[R]:
 .PP
 .TS

documentation/manpages/sdk/dotnet-environment-variables.7

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-environment-variables" "7" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-environment-variables" "7" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH NAME
 .PP
@@ -439,7 +439,7 @@ For more information, see the \f[V]--roll-forward\f[R] option for the \f[V]dotne
 If set to \f[V]1\f[R] (enabled), enables rolling forward to a pre-release version from a release version.
 By default (\f[V]0\f[R] - disabled), when a release version of .NET runtime is requested, roll-forward will only consider installed release versions.
 .PP
-For more information, see the \f[V]--roll-forward\f[R] option for the \f[V]dotnet\f[R] command
+For more information, see the \f[V]--roll-forward\f[R] option for the \f[V]dotnet\f[R] command.
 .SS \f[V]DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX\f[R]
 .PP
 Disables minor version roll forward, if set to \f[V]0\f[R].

documentation/manpages/sdk/dotnet-format.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-format" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-format" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet format
 .PP

documentation/manpages/sdk/dotnet-help.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-help" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-help" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet help reference
 .PP

documentation/manpages/sdk/dotnet-migrate.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-migrate" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-migrate" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet migrate
 .PP
@@ -49,7 +49,7 @@ A single project by specifying the \f[I]project.json\f[R] file to migrate.
 .IP \[bu] 2
 All of the directories specified in the \f[I]global.json\f[R] file by passing in a path to the \f[I]global.json\f[R] file.
 .IP \[bu] 2
-A \f[I]solution.sln\f[R] file, where it migrates the projects referenced in the solution.
+A \f[I]solution.sln(x)\f[R] file, where it migrates the projects referenced in the solution.
 .IP \[bu] 2
 On all subdirectories of the given directory recursively.
 .PP
@@ -72,7 +72,7 @@ a \f[I]project.json\f[R] file to migrate.
 .IP \[bu] 2
 a \f[I]global.json\f[R] file: the folders specified in \f[I]global.json\f[R] are migrated.
 .IP \[bu] 2
-a \f[I]solution.sln\f[R] file: the projects referenced in the solution are migrated.
+a \f[I]solution.sln(x)\f[R] file: the projects referenced in the solution are migrated.
 .IP \[bu] 2
 a directory to migrate: recursively searches for \f[I]project.json\f[R] files to migrate inside the specified directory.
 .PP

documentation/manpages/sdk/dotnet-msbuild.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-msbuild" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-msbuild" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet msbuild
 .PP

documentation/manpages/sdk/dotnet-new-details.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-new-details" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-new-details" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet new details
 .PP
@@ -50,7 +50,7 @@ The package identifier to display the details for.
 By default, \f[V]dotnet new details\f[R] uses the hierarchy of NuGet configuration files from the current directory to determine the NuGet source the package can be installed from.
 If \f[V]--nuget-source\f[R] is specified, the source is added to the list of sources to be checked.
 To check the configured sources for the current directory use \f[V]dotnet nuget list source\f[R].
-For more information, see Common NuGet Configurations
+For more information, see Common NuGet Configurations.
 .RE
 .IP \[bu] 2
 \f[B]\f[VB]--interactive\f[B]\f[R]

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

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-new-install" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-new-install" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet new install
 .PP
@@ -26,7 +26,7 @@ dotnet-new-install - installs a template package.
 .IP
 .nf
 \f[C]
-dotnet new install <PATH|NUGET_ID>  [--interactive] [--add-source|--nuget-source <SOURCE>] [--force] 
+dotnet new install <PATH|NUGET_ID>  [--interactive] [--add-source|--nuget-source <SOURCE>] [--force]
     [-d|--diagnostics] [--verbosity <LEVEL>] [-h|--help]
 \f[R]
 .fi
@@ -85,11 +85,8 @@ If you want to install a specific version or prerelease version of a template pa
 .PP
 By default, \f[V]dotnet new install\f[R] uses the hierarchy of NuGet configuration files from the current directory to determine the NuGet source the package can be installed from.
 If \f[V]--nuget-source\f[R] is specified, the source will be added to the list of sources to be checked.
-.PD 0
-.P
-.PD
 To check the configured sources for the current directory use \f[V]dotnet nuget list source\f[R].
-For more information, see Common NuGet Configurations
+For more information, see Common NuGet Configurations.
 .RS
 .PP
 Following NuGet\[cq]s Https Everywhere (https://devblogs.microsoft.com/nuget/https-everywhere/) initiative, \f[V]dotnet new\f[R] is phasing out \f[V]http\f[R] feeds.
@@ -161,7 +158,7 @@ Install version 2.0 of the SPA templates for ASP.NET Core from a custom NuGet so
 .IP
 .nf
 \f[C]
-dotnet new --install Microsoft.DotNet.Web.Spa.ProjectTemplates::2.0.0 --add-source \[dq]https://api.my-custom-nuget.com/v3/index.json\[dq] --interactive
+dotnet new install Microsoft.DotNet.Web.Spa.ProjectTemplates::2.0.0 --add-source \[dq]https://api.my-custom-nuget.com/v3/index.json\[dq] --interactive
 \f[R]
 .fi
 .RE

documentation/manpages/sdk/dotnet-new-list.1

@@ -14,7 +14,7 @@
 . ftr VB CB
 . ftr VBI CBI
 .\}
-.TH "dotnet-new-list" "1" "2024-10-02" "" ".NET Documentation"
+.TH "dotnet-new-list" "1" "2025-05-30" "" ".NET Documentation"
 .hy
 .SH dotnet new list
 .PP