refresh dotnet command reference to use latest commands and .NET 6 and later versions

meaghanlewis · meaghanlewis · commit ad0e1645379d · 2025-09-29T14:03:38.000-07:00
diff --git a/docs/core/tools/dotnet-dev-certs.md b/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)
diff --git a/docs/core/tools/dotnet-msbuild.md b/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
 
diff --git a/docs/core/tools/dotnet-pack.md b/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
 
@@ -15,11 +15,7 @@ ms.date: 04/04/2024
 
 ```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>]
+    [-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 +60,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 +76,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`**
 
diff --git a/docs/core/tools/dotnet-package-remove.md b/docs/core/tools/dotnet-package-remove.md
@@ -1,23 +1,23 @@
 ---
 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 +28,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 +53,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
+  ```
diff --git a/docs/core/tools/dotnet-restore.md b/docs/core/tools/dotnet-restore.md
@@ -1,7 +1,7 @@
 ---
 title: dotnet restore command
 description: Learn how to restore dependencies and project-specific tools with the dotnet restore command.
-ms.date: 09/24/2025
+ms.date: 09/29/2025
 ---
 # dotnet restore
 
@@ -17,7 +17,7 @@ ms.date: 09/24/2025
 dotnet restore [<PROJECT>|<SOLUTION>|<FILE>] [--configfile <FILE>] [--disable-build-servers]
     [--disable-parallel]
     [-f|--force] [--force-evaluate] [--ignore-failed-sources]
-    [--interactive] [--lock-file-path <LOCK_FILE_PATH>] [--locked-mode]
+    [--interactive] [--lock-file-path <LOCK_FILE_PATH>] [--locked-mode] [--no-http-cache]
     [--no-cache] [--no-dependencies] [--packages <PACKAGES_DIRECTORY>]
     [-r|--runtime <RUNTIME_IDENTIFIER>] [-s|--source <SOURCE>]
     [--tl:[auto|on|off]] [--use-current-runtime, --ucr [true|false]]
@@ -124,6 +124,10 @@ There are three specific settings that `dotnet restore` ignores:
 
   Don't allow updating project lock file.
 
+- **`--no-http-cache`**
+
+  Disable Http Caching for packages.
+
 - **`--no-cache`**
 
   Specifies to not cache HTTP requests.
diff --git a/docs/core/tools/dotnet-run.md b/docs/core/tools/dotnet-run.md
@@ -1,7 +1,7 @@
 ---
 title: dotnet run command
 description: The dotnet run command provides a convenient option to run your application from the source code.
-ms.date: 09/24/2025
+ms.date: 09/29/2025
 ---
 # dotnet run
 
@@ -14,13 +14,10 @@ ms.date: 09/24/2025
 ## Synopsis
 
 ```dotnetcli
-dotnet run [<applicationArguments>] [-a|--arch <ARCHITECTURE>] [-c|--configuration <CONFIGURATION>]
-    [-e|--environment <KEY=VALUE>] [--file <FILE_PATH>]
-    [-f|--framework <FRAMEWORK>] [--force] [--interactive]
-    [--launch-profile <NAME>] [--no-build]
-    [--no-dependencies] [--no-launch-profile] [--no-restore]
-    [--os <OS>] [--project <PATH>] [-r|--runtime <RUNTIME_IDENTIFIER>]
-    [--tl:[auto|on|off]] [-v|--verbosity <LEVEL>]
+dotnet run [<applicationArguments>] [-a|--arch <ARCHITECTURE>] [--artifacts-path <ARTIFACTS_DIR>] [-c|--configuration <CONFIGURATION>]
+    [-e|--environment <KEY=VALUE>] [--file <FILE_PATH>] [-f|--framework <FRAMEWORK>] [--force] [--interactive]
+    [--launch-profile <NAME>] [--no-build] [--no-dependencies] [--no-launch-profile] [--no-restore]
+    [--os <OS>] [--project <PATH>] [-r|--runtime <RUNTIME_IDENTIFIER>] [--tl:[auto|on|off]] [-v|--verbosity <LEVEL>]
     [[--] [application arguments]]
 
 dotnet run -h|--help
@@ -69,8 +66,12 @@ To run the application, the `dotnet run` command resolves the dependencies of th
 
 [!INCLUDE [arch](../../../includes/cli-arch.md)]
 
+[!INCLUDE [artifacts-path](../../../includes/cli-artifacts-path.md)]
+
 [!INCLUDE [configuration](../../../includes/cli-configuration.md)]
 
+[!INCLUDE [disable-build-servers](../../../includes/cli-disable-build-servers.md)]
+
 - **`-e|--environment <KEY=VALUE>`**
 
   Sets the specified environment variable in the process that will be run by the command. The specified environment variable is *not* applied to the `dotnet run` process.
@@ -117,6 +118,10 @@ To run the application, the `dotnet run` command resolves the dependencies of th
 
   Doesn't build the project before running. It also implicitly sets the `--no-restore` flag.
 
+- **`--no-cache`**
+
+  Skip up to date checks and always build the program before running.
+
 - **`--no-dependencies`**
 
   When restoring a project with project-to-project (P2P) references, restores the root project and not the references.
@@ -129,6 +134,10 @@ To run the application, the `dotnet run` command resolves the dependencies of th
 
   Doesn't execute an implicit restore when running the command.
 
+- **`--no-self-contained`**
+
+  Publish your application as a framework dependent application. A compatible .NET runtime must be installed on the target machine to run your application.
+
 [!INCLUDE [os](../../../includes/cli-os.md)]
 
 - **`--project <PATH>`**
@@ -158,6 +167,10 @@ To run the application, the `dotnet run` command resolves the dependencies of th
 
   Specifies the target runtime to restore packages for. For a list of Runtime Identifiers (RIDs), see the [RID catalog](../rid-catalog.md).
 
+- **`-sc|--self-contained`**
+
+  Publishes the .NET runtime with your application so the runtime doesn't need to be installed on the target system. The default is `false`.  However, when targeting .NET 7 or lower, the default is `true` if a runtime identifier is specified.
+
 [!INCLUDE [tl](../../../includes/cli-tl.md)]
 
 [!INCLUDE [verbosity](../../../includes/cli-verbosity-minimal.md)]
diff --git a/docs/core/tools/dotnet-store.md b/docs/core/tools/dotnet-store.md
@@ -1,11 +1,11 @@
 ---
 title: dotnet store command
 description: The 'dotnet store' command stores the specified assemblies in the runtime package store.
-ms.date: 02/14/2020
+ms.date: 09/29/2025
 ---
 # dotnet store
 
-**This article applies to:** ✔️ .NET Core 3.1 SDK and later versions
+**This article applies to:** ✔️ .NET 6 and later versions
 
 ## Name
 
@@ -14,10 +14,10 @@ ms.date: 02/14/2020
 ## Synopsis
 
 ```dotnetcli
-dotnet store -m|--manifest <PATH_TO_MANIFEST_FILE>
-    -f|--framework <FRAMEWORK_VERSION> -r|--runtime <RUNTIME_IDENTIFIER>
+dotnet store [-m|--manifest <PATH_TO_MANIFEST_FILE>]
+    [-f|--framework <FRAMEWORK_VERSION>] [--disable-build-servers] [-r|--runtime <RUNTIME_IDENTIFIER>]
     [--framework-version <FRAMEWORK_VERSION>] [--output <OUTPUT_DIRECTORY>]
-    [--skip-optimization] [--skip-symbols] [-v|--verbosity <LEVEL>]
+    [--skip-optimization] [--skip-symbols] [--use-current-runtime, --ucr [true|false]] [-v|--verbosity <LEVEL>]
     [--working-dir <WORKING_DIRECTORY>]
 
 dotnet store -h|--help
@@ -33,6 +33,8 @@ dotnet store -h|--help
 
   Specifies the [target framework](../../standard/frameworks.md). The target framework has to be specified in the project file.
 
+[!INCLUDE [disable-build-servers](../../../includes/cli-disable-build-servers.md)]
+
 - **`-m|--manifest <PATH_TO_MANIFEST_FILE>`**
 
   The *package store manifest file* is an XML file that contains the list of packages to store. The format of the manifest file is compatible with the SDK-style project format. So, a project file that references the desired packages can be used with the `-m|--manifest` option to store assemblies in the runtime package store. To specify multiple manifest files, repeat the option and path for each file. For example: `--manifest packages1.csproj --manifest packages2.csproj`.
@@ -61,6 +63,10 @@ dotnet store -h|--help
 
   Skips symbol generation. Currently, you can only generate symbols on Windows and Linux.
 
+- **`--use-current-runtime, --ucr [true|false]`**
+
+  Use current runtime as the target runtime. The default is `false`.
+
 [!INCLUDE [verbosity](../../../includes/cli-verbosity.md)]
 
 - **`-w|--working-dir <WORKING_DIRECTORY>`**
diff --git a/docs/core/tools/dotnet-test.md b/docs/core/tools/dotnet-test.md
@@ -1,7 +1,7 @@
 ---
 title: dotnet test command
 description: The dotnet test command is used to execute unit tests in a given project.
-ms.date: 03/27/2024
+ms.date: 09/29/2025
 ---
 # dotnet test
 
@@ -35,7 +35,7 @@ Some examples of the `dotnet.config` file:
 
 ### [dotnet test with VSTest](#tab/dotnet-test-with-vstest)
 
-**This article applies to:** ✔️ .NET Core 3.1 SDK and later versions
+**This article applies to:** ✔️ .NET 6 and later versions
 
 #### Synopsis
 
@@ -54,6 +54,7 @@ dotnet test [<PROJECT> | <SOLUTION> | <DIRECTORY> | <DLL> | <EXE>]
     [-c|--configuration <CONFIGURATION>]
     [--collect <DATA_COLLECTOR_NAME>]
     [-d|--diag <LOG_FILE>]
+    [--disable-build-servers]
     [-f|--framework <FRAMEWORK>]
     [-e|--environment <NAME="VALUE">]
     [--filter <EXPRESSION>]
@@ -186,6 +187,8 @@ Where `Microsoft.NET.Test.Sdk` is the test host, `xunit` is the test framework.
 
   Enables diagnostic mode for the test platform and writes diagnostic messages to the specified file and to files next to it. The process that is logging the messages determines which files are created, such as `*.host_<date>.txt` for test host log, and `*.datacollector_<date>.txt` for data collector log.
 
+[!INCLUDE [disable-build-servers](../../../includes/cli-disable-build-servers.md)]
+
 - **`-e|--environment <NAME="VALUE">`**
 
   Sets the value of an environment variable. Creates the variable if it does not exist, overrides if it does exist. Use of this option will force the tests to be run in an isolated process. The option can be specified multiple times to provide multiple variables.
diff --git a/docs/core/tools/dotnet-watch.md b/docs/core/tools/dotnet-watch.md
