Merge branch 'main' of https://github.com/dotnet/sdk into merge/release/9.0.3xx-to-main

Author: Jason Zhai

documentation/general/dotnet-run-file.md

@@ -71,11 +71,11 @@ We want to report an error for non-entry-point files to avoid the confusion of b
 
 Internally, the SDK CLI detects entry points by parsing all `.cs` files in the directory tree of the entry point file with default parsing options (in particular, no `<DefineConstants>`)
 and checking which ones contain top-level statements (`Main` methods are not supported for now as that would require full semantic analysis, not just parsing).
-Results of this detection are used to exclude other entry points from [builds](#multiple-entry-points) and [app directive collection](#directives-for-project-metadata).
+Results of this detection are used to exclude other entry points from [builds](#multiple-entry-points) and [file-level directive collection](#directives-for-project-metadata).
 This means the CLI might consider a file to be an entry point which later the compiler doesn't
 (for example because its top-level statements are under `#if !SYMBOL` and the build has `DefineConstants=SYMBOL`).
 However such inconsistencies should be rare and hence that is a better trade off than letting the compiler decide which files are entry points
-because that could require multiple builds (first determine entry points and then re-build with app directives except those from other entry points).
+because that could require multiple builds (first determine entry points and then re-build with file-level directives except those from other entry points).
 To avoid parsing all C# files twice (in CLI and in the compiler), the CLI could use the compiler server for parsing so the trees are reused
 (unless the parse options change via the directives), and also [cache](#optimizations) the results to avoid parsing on subsequent runs.
 
@@ -146,7 +146,7 @@ They are not cleaned immediately because they can be re-used on subsequent runs
 
 ## Directives for project metadata
 
-It is possible to specify some project metadata via *app directives*
+It is possible to specify some project metadata via *file-level directives*
 which are [ignored][ignored-directives] by the C# language but recognized by the SDK CLI.
 Directives `sdk`, `package`, and `property` are translated into `<Project Sdk="...">`, `<PackageReference>`, and `<Property>` project elements, respectively.
 Other directives result in an error, reserving them for future use.

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