Update dotnet command reference

.openpublishing.redirection.core.json

@@ -1516,6 +1516,10 @@
         {
             "source_path_from_root": "/docs/core/compatibility/sdk/9.0/nugetaudit-transitive-packages.md",
             "redirect_url": "/dotnet/core/compatibility/sdk/10.0/nugetaudit-transitive-packages"
+        },
+        {
+            "source_path_from_root": "/docs/core/tools/dotnet-migrate.md",
+            "redirect_url": "/dotnet/core/porting"
         }
     ]
 }

docs/core/compatibility/sdk/10.0/dotnet-restore-project-json-unsupported.md

@@ -30,15 +30,15 @@ This change can affect [source compatibility](../../categories.md#source-compati
 
 The `project.json` format was originally available only in .NET Core previews (through Preview 2 of .NET Core 1.0) and was completely replaced by PackageReference in 2017. The format has been marked as deprecated since 2017.
 
-When the `project.json` format was replaced, users migrated these projects using the [`dotnet migrate`](../../../tools/dotnet-migrate.md) command, but that command was removed from the CLI in the .NET Core 3.0 SDK.
+When the `project.json` format was replaced, users migrated these projects using the `dotnet migrate` command, but that command was removed from the CLI in the .NET Core 3.0 SDK.
 
 The removal of `project.json` support completes this transition and allows the .NET team to focus on delivering a better experience for PackageReference-based projects.
 
 ## Recommended action
 
 Migrate your `project.json` projects to use PackageReference format instead.
 
-If you have .NET Core based `project.json` projects, you can use older versions of the .NET SDK that still include the [`dotnet migrate` command](../../../tools/dotnet-migrate.md) to convert them to the modern project format.
+If you have .NET Core based `project.json` projects, you can use older versions of the .NET SDK that still include the `dotnet migrate` to convert them to the modern project format.
 
 For more information about migrating from `project.json`, see [Migrating from project.json to .csproj](/nuget/archive/project-json#migrate-projectjson-to-packagereference).
 

docs/core/tools/dotnet-dev-certs.md

@@ -1,11 +1,11 @@
 ---
 title: dotnet dev-certs command
 description: The dotnet dev-certs command generates a self-signed certificate to enable HTTPS use in development.
-ms.date: 07/14/2022
+ms.date: 09/25/2025
 ---
 # dotnet dev-certs
 
-**This article applies to:** ✔️ .NET Core 3.1 SDK and later versions
+**This article applies to:** ✔️ .NET 6 and later versions
 
 ## Name
 
@@ -18,7 +18,7 @@ dotnet dev-certs https
   [-c|--check] [--clean] [-ep|--export-path <PATH>]
   [--format] [-i|--import] [-np|--no-password]
   [-p|--password] [-q|--quiet] [-t|--trust]
-  [-v|--verbose] [--version]
+  [-v|--verbose] [--version] [--check-trust-machine-readable]
 
 dotnet dev-certs https -h|--help
 ```
@@ -140,6 +140,10 @@ The `dotnet dev-certs` command manages a self-signed certificate to enable HTTPS
 
   Display debug information.
 
+- **`--check-trust-machine-readable`**
+
+  Same as running `--check --trust`, but outputs the results in json.  
+
 ## Examples
 
 - Check for the presence of a development certificate, and create one in the default certificate store if one doesn't exist yet. But don't trust the certificate.
@@ -188,8 +192,8 @@ The `dotnet dev-certs` command manages a self-signed certificate to enable HTTPS
 
 ## See also
 
-* [Generate self-signed certificates with the .NET CLI](../additional-tools/self-signed-certificates-guide.md)
-* [Enforce HTTPS in ASP.NET Core](/aspnet/core/security/enforcing-ssl)
-* [Troubleshoot certificate problems such as certificate not trusted](/aspnet/core/security/enforcing-ssl#troubleshoot-certificate-problems-such-as-certificate-not-trusted)
-* [Hosting ASP.NET Core images with Docker over HTTPS](/aspnet/core/security/docker-https)
-* [Hosting ASP.NET Core images with Docker Compose over HTTPS](/aspnet/core/security/docker-compose-https)
+- [Generate self-signed certificates with the .NET CLI](../additional-tools/self-signed-certificates-guide.md)
+- [Enforce HTTPS in ASP.NET Core](/aspnet/core/security/enforcing-ssl)
+- [Troubleshoot certificate problems such as certificate not trusted](/aspnet/core/security/enforcing-ssl#troubleshoot-certificate-problems-such-as-certificate-not-trusted)
+- [Hosting ASP.NET Core images with Docker over HTTPS](/aspnet/core/security/docker-https)
+- [Hosting ASP.NET Core images with Docker Compose over HTTPS](/aspnet/core/security/docker-compose-https)

docs/core/tools/dotnet-format.md

@@ -1,11 +1,11 @@
 ---
 title: dotnet format command
 description: The dotnet format command formats code to match EditorConfig settings for the current directory.
-ms.date: 07/12/2021
+ms.date: 09/25/2025
 ---
 # dotnet format
 
-**This article applies to:** ✔️ .NET 6.x SDK and later versions
+**This article applies to:** ✔️ .NET 6 and later versions
 
 ## Name
 
@@ -14,7 +14,7 @@ ms.date: 07/12/2021
 ## Synopsis
 
 ```dotnetcli
-dotnet format [<PROJECT | SOLUTION>] [command] [options]
+dotnet format [<PROJECT | SOLUTION>] [--diagnostics <DIAGNOSTICS>] [--exclude-diagnostics <EXCLUDE-DIAGNOSTICS>] [--severity <SEVERITY>] [--no-restore] [--verify-no-changes] [--include <INCLUDE>] [--exclude <EXCLUDE>] [--include-generated] [-v|--verbosity <LEVEL>] [--binarylog <BINARY-LOG-PATH>] [--report <REPORT-PATH>] [--version]
 
 dotnet format -h|--help
 ```
@@ -33,49 +33,55 @@ The MSBuild project or solution to run code formatting on. If a project or solut
 
 None of the options below are required for the `dotnet format` command to succeed, but you can use them to further customize what is formatted and by which rules.
 
-* **`--diagnostics <DIAGNOSTICS>`**
+- **`--diagnostics <DIAGNOSTICS>`**
 
   A space-separated list of diagnostic IDs to use as a filter when fixing code style or third-party issues. Default value is whichever IDs are listed in the *.editorconfig* file. For a list of built-in analyzer rule IDs that you can specify, see the [list of IDs for code-analysis style rules](../../fundamentals/code-analysis/style-rules/index.md).
 
-* **`--severity`**
+- **`--exclude-diagnostics <EXCLUDE-DIAGNOSTICS>`**
+
+  A space-separated list of diagnostic IDs to exclude when fixing code style or third-party issues. Default value is none. For a list of built-in analyzer rule IDs that you can specify, see the [list of IDs for code-analysis style rules](../../fundamentals/code-analysis/style-rules/index.md).
+
+- **`--severity`**
 
   The minimum severity of diagnostics to fix. Allowed values are `info`, `warn`, and `error`. The default value is `warn`.
 
-* **`--no-restore`**
+- **`--no-restore`**
 
   Doesn't execute an implicit restore before formatting. Default is to do implicit restore.
 
-* **`--verify-no-changes`**
+- **`--verify-no-changes`**
 
   Verifies that no formatting changes would be performed. Terminates with a non zero exit code if any files would have been formatted.
 
-* **`--include <INCLUDE>`**
+- **`--include <INCLUDE>`**
 
   A space-separated list of relative file or folder paths to include in formatting. The default is all files in the solution or project.
 
-* **`--exclude <EXCLUDE>`**
+- **`--exclude <EXCLUDE>`**
 
   A space-separated list of relative file or folder paths to exclude from formatting. The default is none.
 
-* **`--include-generated`**
+- **`--include-generated`**
 
   Formats files generated by the SDK.
 
-* **`-v|--verbosity <LEVEL>`**
+- **`-v|--verbosity <LEVEL>`**
 
   Sets the verbosity level. Allowed values are `q[uiet]`, `m[inimal]`, `n[ormal]`, `d[etailed]`, and `diag[nostic]`. Default value is `m[inimal]`.
 
-* **`--binarylog <BINARY-LOG-PATH>`**
+- **`--binarylog <BINARY-LOG-PATH>`**
 
   Logs all project or solution load information to a binary log file.
 
-* **`--report <REPORT-PATH>`**
+- **`--report <REPORT-PATH>`**
 
   Produces a JSON report in the directory specified by `<REPORT_PATH>`.
 
-* **`-h|--help`**
+- **`--version`**
+
+  Displays version information.
 
-  Shows help and usage information
+[!INCLUDE [help](../../../includes/cli-help.md)]
 
 ## Subcommands
 
@@ -89,7 +95,7 @@ The `dotnet format whitespace` subcommand only runs formatting rules associated
 
 #### Options
 
-* **`--folder`**
+- **`--folder`**
 
   Treat the `<PROJECT | SOLUTION>` argument as a path to a simple folder of code files.
 
@@ -103,11 +109,11 @@ The `dotnet format style` subcommand only runs formatting rules associated with
 
 #### Options
 
-* **`--diagnostics <DIAGNOSTICS>`**
+- **`--diagnostics <DIAGNOSTICS>`**
 
   A space-separated list of diagnostic IDs to use as a filter when fixing code style issues. Default value is whichever IDs are listed in the *.editorconfig* file. For a list of built-in code style analyzer rule IDs that you can specify, see the [list of IDs for code-analysis style rules](../../fundamentals/code-analysis/style-rules/index.md).
 
-* **`--severity`**
+- **`--severity`**
 
   The minimum severity of diagnostics to fix. Allowed values are `info`, `warn`, and `error`. The default value is `warn`
 
@@ -121,59 +127,59 @@ The `dotnet format analyzers` subcommand only runs formatting rules associated w
 
 ##### Options
 
-* **`--diagnostics <DIAGNOSTICS>`**
+- **`--diagnostics <DIAGNOSTICS>`**
 
   A space-separated list of diagnostic IDs to use as a filter when fixing non code style issues. Default value is whichever IDs are listed in the *.editorconfig* file. For a list of built-in analyzer rule IDs that you can specify, see the [list of IDs for quality rules](../../fundamentals/code-analysis/quality-rules/index.md). For third-party analyzers refer to their documentation.
 
-* **`--severity`**
+- **`--severity`**
 
   The minimum severity of diagnostics to fix. Allowed values are `info`, `warn`, and `error`. The default value is `warn`.
 
 ## Examples
 
-* Format all code in the solution:
+- Format all code in the solution:
 
   ```dotnetcli
   dotnet format ./solution.sln
   ```
 
-* Clean up all code in the application project:
+- Clean up all code in the application project:
 
   ```dotnetcli
   dotnet format ./src/application.csproj
   ```
 
-* Verify that all code is correctly formatted:
+- Verify that all code is correctly formatted:
 
   ```dotnetcli
   dotnet format --verify-no-changes
   ```
 
-* Clean up all code in the *src* and *tests* directory but not in *src/submodule-a*:
+- Clean up all code in the *src* and *tests* directory but not in *src/submodule-a*:
 
   ```dotnetcli
   dotnet format --include ./src/ ./tests/ --exclude ./src/submodule-a/
   ```
 
-* Fix a specific **code style** issue:  
+- Fix a specific **code style** issue:  
 
   ```dotnetcli
   dotnet format style --diagnostics IDE0005 --severity info
   ```
 
-* Fix all **code style** issues that have severity `info`, `warning` or `error`:
+- Fix all **code style** issues that have severity `info`, `warning` or `error`:
 
   ```dotnetcli
   dotnet format style --severity info
   ```
 
-* Fix a specific (non code style) analyzer issue:
+- Fix a specific (non code style) analyzer issue:
 
   ```dotnetcli  
   dotnet format analyzers --diagnostics CA1831 --severity warn
   ```
 
-* Fix all non code style issues that have severity `info`, `warning` or `error`:  
+- Fix all non code style issues that have severity `info`, `warning` or `error`:  
 
   ```dotnetcli  
   dotnet format analyzers --severity info

docs/core/tools/dotnet-msbuild.md

@@ -1,11 +1,11 @@
 ---
 title: dotnet msbuild command
 description: The dotnet msbuild command provides access to the MSBuild command line.
-ms.date: 02/14/2020
+ms.date: 09/25/2025
 ---
 # dotnet msbuild
 
-**This article applies to:** ✔️ .NET Core 3.1 SDK and later versions
+**This article applies to:** ✔️ .NET 6 and later versions
 
 ## Name