Refresh dotnet command reference

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/29/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/29/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,8 @@ 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 +34,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 +96,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 +110,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 +128,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/29/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
 

docs/core/tools/dotnet-pack.md

@@ -1,11 +1,11 @@
 ---
 title: dotnet pack command
 description: The dotnet pack command creates NuGet packages for your .NET project.
-ms.date: 04/04/2024
+ms.date: 09/29/2025
 ---
 # dotnet pack
 
-**This article applies to:** ✔️ .NET Core 3.1 SDK and later versions
+**This article applies to:** ✔️ .NET 6 and later versions
 
 ## Name
 
@@ -14,13 +14,10 @@ ms.date: 04/04/2024
 ## Synopsis
 
 ```dotnetcli
-dotnet pack [<PROJECT>|<SOLUTION>] [--artifacts-path <ARTIFACTS_DIR>]
-    [-c|--configuration <CONFIGURATION>] [--force]
-    [--include-source] [--include-symbols] [--interactive]
-    [--no-build] [--no-dependencies] [--no-restore] [--nologo]
-    [-o|--output <OUTPUT_DIRECTORY>] [--runtime <RUNTIME_IDENTIFIER>]
-    [-s|--serviceable] [--tl:[auto|on|off]] [-v|--verbosity <LEVEL>]
-    [--version-suffix <VERSION_SUFFIX>]
+dotnet pack [<PROJECT>|<SOLUTION>]
+  [--artifacts-path <ARTIFACTS_DIR>]
+  [-c|--configuration <CONFIGURATION>] [--disable-build-servers][--force] [--include-source] [--include-symbols] [--interactive] [--no-build] [--no-dependencies] [--no-restore] [--nologo] [-o|--output <OUTPUT_DIRECTORY>] [--runtime <RUNTIME_IDENTIFIER>] [-s|--serviceable] [--tl:[auto|on|off]] [-v|--verbosity <LEVEL>]
+  [--version-suffix <VERSION_SUFFIX>]
 
 dotnet pack -h|--help
 ```
@@ -64,6 +61,8 @@ You can provide MSBuild properties to the `dotnet pack` command for the packing
 
 [!INCLUDE [configuration](../../../includes/cli-configuration-publish-pack.md)]
 
+[!INCLUDE [disable-build-servers](../../../includes/cli-disable-build-servers.md)]
+
 - **`--force`**
 
   Forces all dependencies to be resolved even if the last restore was successful. Specifying this flag is the same as deleting the *project.assets.json* file.
@@ -78,7 +77,7 @@ You can provide MSBuild properties to the `dotnet pack` command for the packing
 
   Includes the debug symbols NuGet packages in addition to the regular NuGet packages in the output directory.
 
-[!INCLUDE [interactive](../../../includes/cli-interactive-3-0.md)]
+[!INCLUDE [interactive](../../../includes/cli-interactive.md)]
 
 - **`--no-build`**
 

docs/core/tools/dotnet-package-remove.md

@@ -1,23 +1,24 @@
 ---
 title: dotnet package remove command
 description: The dotnet package remove command provides a convenient option to remove NuGet package reference to a project.
-ms.date: 04/02/2025
+ms.date: 09/29/2025
 ---
 # dotnet package remove
 
-**This article applies to:** ✔️ .NET Core 3.1 SDK and later versions
+**This article applies to:** ✔️ .NET 6 and later versions
 
 ## Name
 
-`dotnet package remove` - Removes package reference from a project file.
+`dotnet package remove` - Removes a package reference from a project file.
 
 > [!NOTE]
 > If you're using .NET 9 SDK or earlier, use the "verb first" form (`dotnet remove package`) instead. The "noun first" form was introduced in .NET 10. For more information, see [More consistent command order](../whats-new/dotnet-10/sdk.md#more-consistent-command-order).
 
 ## Synopsis
 
 ```dotnetcli
-dotnet package remove <PACKAGE_NAME> [--project <PROJECT>]
+dotnet package remove <PACKAGE_NAME> [--project <PROJECT>]  
+  [--interactive] [--file <FILE>]
 
 dotnet package remove -h|--help
 ```
@@ -28,16 +29,22 @@ The `dotnet package remove` command provides a convenient option to remove a NuG
 
 ## Arguments
 
-`PROJECT`
-
-Specifies the project file. If not specified, the command searches the current directory for one.
-
 `PACKAGE_NAME`
 
 The package reference to remove.
 
 ## Options
 
+- **`-p|--project <PROJECT>`**
+
+  The project file to operate on. If a solution file is specified, the command will update the package in all projects in the solution that reference it. If not specified, the command will search the current directory for a project file.
+
+[!INCLUDE [interactive](../../../includes/cli-interactive.md)]
+
+- **`--file <FILE>`**
+
+  The file-based app to operate on.
+
 [!INCLUDE [help](../../../includes/cli-help.md)]
 
 ## Examples
@@ -47,3 +54,9 @@ The package reference to remove.
   ```dotnetcli
   dotnet package remove Newtonsoft.Json
   ```
+
+- Remove `Newtonsoft.Json` NuGet package from a specific project file:
+
+  ```dotnetcli
+  dotnet package remove Newtonsoft.Json --file MyApp.cs
+  ```