Merge pull request #14176 from cdpark/refresh-vs-2022

Feature 474055: Q&M: Freshness work for VS, 3 articles

Author: JamesJBarnett

docs/ide/reference/command-prompt-powershell.md

@@ -1,9 +1,9 @@
 ---
-title: 'Command-line shells & prompt for developers'
-description:  Start from the Tools > Command Line menu. Select the Visual Studio Developer Command Prompt, Developer PowerShell, or terminal to use .NET and C++ tools more easily.
+title: Command-Line Shells & Prompt For Developers
+description: Learn about the two command-line shells for developers in Visual Studio, the Developer Command Prompt and the Developer PowerShell.
 author: Mikejo5000
 ms.author: mikejo
-ms.date: 08/23/2024
+ms.date: 08/06/2025
 ms.topic: conceptual
 helpviewer_keywords:
   - "Visual Studio command prompt"
@@ -19,23 +19,23 @@ ms.subservice: general-ide
 
 Visual Studio includes two command-line shells for developers, a command prompt and an instance of PowerShell, as follows:
 
-- **Visual Studio Developer Command Prompt** - A standard command prompt with certain environment variables set to make using command-line developer tools easier.
+- **Visual Studio Developer Command Prompt**: A standard command prompt with certain environment variables set to make using command-line developer tools easier.
 
     ::: moniker range="vs-2019"
-    :::image type="content" source="media/developer-command-prompt-for-vs/command-prompt.png" alt-text="Screenshot of the Developer Command Prompt for Visual Studio 2019 showing clrver tool.":::
+    :::image type="content" source="media/developer-command-prompt-for-vs/command-prompt.png" alt-text="Screenshot of the Developer Command Prompt for Visual Studio 2019.":::
     ::: moniker-end
 
     ::: moniker range=">=vs-2022"
-    :::image type="content" source="media/developer-command-prompt-for-vs/developer-command-prompt-visual-studio-2022.png" alt-text="Screenshot of the Developer Command Prompt for Visual Studio that shows the clrver tool.":::
+    :::image type="content" source="media/developer-command-prompt-for-vs/developer-command-prompt-visual-studio-2022.png" alt-text="Screenshot of the Developer Command Prompt for Visual Studio.":::
     ::: moniker-end
 
-- **Visual Studio Developer PowerShell** - More powerful than a command prompt. For example, you can pass the output of one command (known as a *cmdlet*) to another cmdlet. This shell has the same environment variables set as Developer Command Prompt. Available since Visual Studio 2019.
+- **Visual Studio Developer PowerShell**: More powerful than a command prompt. For example, you can pass the output of one command, known as a *cmdlet*, to another cmdlet. This shell has the same environment variables set as Developer Command Prompt. Available since Visual Studio 2019.
 
     ::: moniker range=">=vs-2022"
     :::image type="content" source="media/developer-command-prompt-for-vs/developer-powershell-visual-studio-2022.png" alt-text="Screenshot of the Developer PowerShell tool in Visual Studio 2022 and later.":::
     ::: moniker-end
 
-Starting in [Visual Studio 2019](https://devblogs.microsoft.com/visualstudio/say-hello-to-the-new-visual-studio-terminal/), Visual Studio includes an integrated **terminal** that can host either of these shells (Developer Command Prompt and Developer PowerShell). You can also open multiple tabs of each shell. The Visual Studio terminal is built on top of [Windows Terminal](/windows/terminal/). To open the terminal in Visual Studio, select **View** > **Terminal**.
+Starting in Visual Studio 2019, Visual Studio includes an [integrated terminal](https://devblogs.microsoft.com/visualstudio/say-hello-to-the-new-visual-studio-terminal/) that can host either of these command-line shells. You can also open multiple tabs of each shell. The Visual Studio terminal is built on top of [Windows Terminal](/windows/terminal/). To open the terminal in Visual Studio, select **View** > **Terminal**.
 
 ::: moniker range=">=vs-2022"
 :::image type="content" source="media/developer-command-prompt-for-vs/visual-studio-2022-terminal-window.png" alt-text="Screenshot of the Visual Studio terminal pane that shows multiple tabs.":::
@@ -50,7 +50,7 @@ Starting in [Visual Studio 2019](https://devblogs.microsoft.com/visualstudio/say
 
 When you open one of the developer shells from Visual Studio, either as a separate app or in the Terminal window, it opens to the directory of your current solution (if you have a solution loaded). This behavior makes it convenient to run commands against the solution or its projects.
 
-Both shells have specific environment variables set that enable you to use command-line developer tools more easily. After opening one of these shells, you can enter the commands for different utilities without having to know where they're located.
+Both shells have specific environment variables that enable you to use command-line developer tools more easily. After opening one of these shells, you can enter the commands for different utilities without having to know where they're located.
 
 |Popular commands|Description|
 |--|--|
@@ -73,52 +73,44 @@ Follow these steps to open Developer Command Prompt or Developer PowerShell from
 1. On the menu bar, select **Tools** > **Command Line** > **Developer Command Prompt** or **Developer PowerShell**.
 
     ::: moniker range=">=vs-2022"
-    :::image type="content" source="media/developer-command-prompt-for-vs/visual-studio-2022-command-line-menu.png" alt-text="Screenshot of the Command Line menu in Visual Studio 2022 and later.":::
+    :::image type="content" source="media/developer-command-prompt-for-vs/visual-studio-2022-command-line-menu.png" alt-text="Screenshot of the Command Line menu in Visual Studio.":::
     ::: moniker-end
 
     ::: moniker range="vs-2019" 
-    ![Screenshot of the Command Line menu in Visual Studio 2019.](./media/developer-command-prompt-for-vs/vs-menu.png)
-   ::: moniker-end
-   
+    :::image type="content" source="media/developer-command-prompt-for-vs/vs-menu.png" alt-text="Screenshot of the Command Line menu in Visual Studio 2019.":::
+    ::: moniker-end
+
 ## Start from Windows menu
 
-Another way to start the shells is from the Start menu. You may have multiple command prompts, depending on the version of Visual Studio and any additional SDKs and workloads you've installed.
+Another way to start the shells is from the Start menu. You could have multiple command prompts, depending on the version of Visual Studio and any other SDKs and workloads you've installed.
 
 ### Windows 11
 
-1. Select **Start** :::image type="content" source="media/developer-command-prompt-for-vs/windows-11-logo-button.png" alt-text="Screenshot of the Start button in Windows 11.":::, and then in the **Type here to search** dialog box, enter either `developer command prompt` or `developer powershell`.
+1. Select **Start**, and then in the **Type here to search** dialog box, enter either `developer command prompt` or `developer powershell`.
 
 1. Select the App result that's associated with your search text.
 
 ### Windows 10
 
-1. Select **Start** ![Screenshot of the Start button in Windows 10.](./media/developer-command-prompt-for-vs/windows-logo-key-graphic.png), and then scroll to the letter **V**.
+1. Select **Start**, and then scroll to the letter **V**.
 
 1. Expand the **Visual Studio 2019** or **Visual Studio 2022** folder.
 
 1. If you're running Visual Studio 2019, select either **Developer Command Prompt for VS 2019** or **Developer PowerShell for VS 2019**. If you're running Visual Studio 2022, select either **Developer Command Prompt for VS 2022** or **Developer PowerShell for VS 2022**.
 
    Alternatively, you can start typing the name of the shell in the search box on the taskbar, and select the result you want as the result list starts to display the search matches.
 
-   ![An animation that shows the search behavior in Windows 10.](./media/developer-command-prompt-for-vs/windows-10-search.gif)
-   
-### Windows 8.1
-
-1. Go to the **Start** screen, by pressing the Windows logo key ![Screenshot of the Windows logo key on the keyboard.](./media/developer-command-prompt-for-vs/windows-logo-key-graphic.png) on your keyboard for example.
-
-1. On the **Start** screen, press **Ctrl**+**Tab** to open the **Apps** list, and then press **V**. This brings up a list that includes all installed Visual Studio command prompts.
-
-1. If you're running Visual Studio 2019, select either **Developer Command Prompt for VS 2019** or **Developer PowerShell for VS 2019**. If you're running Visual Studio 2022, select **Developer Command Prompt for VS 2022** or **Developer PowerShell for VS 2022**.
+   :::image type="content" source="media/developer-command-prompt-for-vs/windows-10-search.gif" alt-text="Animation that shows the search behavior in Windows 10.":::
 
 ## Start from file browser
 
-Usually, the shortcuts for the shells you have installed are placed in the **Start Menu** folder for Visual Studio, such as in *%ProgramData%\Microsoft\Windows\Start Menu\Programs\Visual Studio 2019\Visual Studio Tools*. But if searching for the command prompt doesn't produce the expected results, you can try to manually locate the files on your machine.
+Usually, the shortcuts for the shells you installed are placed in the **Start Menu** folder for Visual Studio, such as in *%ProgramData%\Microsoft\Windows\Start Menu\Programs\Visual Studio 2019\Visual Studio Tools*. But if searching for the command prompt doesn't produce the expected results, you can try to manually locate the files on your machine.
 
 ### Developer Command Prompt
 
 Search for the name of the command prompt file, which is *VsDevCmd.bat*, or go to the Tools folder for Visual Studio, such as *%ProgramFiles%\Microsoft Visual Studio\2022\Community\Common7\Tools* (the path changes according to your Visual Studio version, edition, and installation location).
 
-Once you've located the command prompt file, open it by entering the following command in a regular command prompt window:
+After you locate the command prompt file, open it by entering the following command in a regular command prompt window:
 
 ::: moniker range="vs-2022"
 
@@ -148,21 +140,22 @@ Or enter the following command in the Windows **Run** dialog box:
 
 ::: moniker-end  
 
-Since Visual Studio 2015, the Developer Command Prompt sets the `VSCMD_VER` environment variable which contains the version information for Visual Studio (ex: `17.9.0`). If you need to detect whether the Developer Command Prompt has already been run in your console, it is recommended to check whether `VSCMD_VER` has been defined or not.
+Since Visual Studio 2015, the Developer Command Prompt sets the `VSCMD_VER` environment variable, which contains the version information for Visual Studio (for example: 17.14.8). If you need to detect whether the Developer Command Prompt was already run in your console, it's recommended to check whether `VSCMD_VER` has been defined or not.
 
 > [!TIP]
 > Make sure to edit the path to match the version or edition of Visual Studio that you're using.
 
 ### Developer PowerShell
 
-Search for a PowerShell script file named *Launch-VsDevShell.ps1*, or go to the Tools folder for Visual Studio, such as *%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\Common7\Tools*. (The path changes according to your Visual Studio version, edition, and installation location.) Once you've located the PowerShell file, run it by entering the following command at a Windows PowerShell or PowerShell 6 prompt.
+Search for a PowerShell script file named *Launch-VsDevShell.ps1*, or go to the Tools folder for Visual Studio, such as *%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\Common7\Tools*. The path changes according to your Visual Studio version, edition, and installation location. After you locate the PowerShell file, run it by entering the following command at a Windows PowerShell or PowerShell 6 prompt.
 
 ::: moniker range="vs-2022"
 For Visual Studio 2022:
 
 ```powershell
 & 'C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\Tools\Launch-VsDevShell.ps1'
 ```
+
 ::: moniker-end
 
 For Visual Studio 2019:
@@ -176,18 +169,18 @@ By default, the Developer PowerShell that launches is configured for the Visual
 > [!TIP]
 > The [execution policy](/powershell/module/microsoft.powershell.core/about/about_execution_policies) must be set in order for the cmdlet to run.
 
-The `Launch-VsDevShell.ps1` script works by locating the `Microsoft.VisualStudio.DevShell.dll` PowerShell module in the Visual Studio installation path, loading it, and then invoking the `Enter-VsDevShell` cmdlet. Installed shortcuts, like those in the Start menu, load the module and invoke the cmdlet directly. `Launch-VsDevShell.ps1` is the recommended way to initialize Developer PowerShell interactively or for scripting build automation.
+The *Launch-VsDevShell.ps1* script works by locating the *Microsoft.VisualStudio.DevShell.dll* PowerShell module in the Visual Studio installation path, loading it, and then invoking the `Enter-VsDevShell` cmdlet. Installed shortcuts, like those in the Start menu, load the module and invoke the cmdlet directly. *Launch-VsDevShell.ps1* is the recommended way to initialize Developer PowerShell interactively or for scripting build automation.
 
 ## Command-line arguments
 
-You can use command-line arguments for either of the shells, Developer Command Prompt or Developer PowerShell.
+You can use command-line arguments for either of the shells: Developer Command Prompt or Developer PowerShell.
 
 ### Target Architecture and Host Architecture
 
-For build tools -- like the C++ compiler -- that create outputs targeting specific CPU architectures, the developer shells can be configured using the appropriate command-line argument. The architecture of the build tool binaries can also be configured by using command-line arguments. This is useful when the build machine is a different architecture than the target architecture.
+For build tools, like the C++ compiler, that create outputs targeting specific CPU architectures, the developer shells can be configured using the appropriate command-line argument. The architecture of the build tool binaries can also be configured by using command-line arguments. This is useful when the build machine is a different architecture than the target architecture.
 
 > [!TIP]
-> Beginning with Visual Studio 2022, `msbuild` will default to a 64-bit msbuild.exe binary, regardless of the Host Architecture.
+> Beginning with Visual Studio 2022, `msbuild` defaults to a 64-bit *msbuild.exe* binary, regardless of the Host Architecture.
 
 |Shell|Argument|
 |--|--|
@@ -197,7 +190,7 @@ For build tools -- like the C++ compiler -- that create outputs targeting specif
 |Developer PowerShell|-HostArch <Host Architecture>|
 
 > [!IMPORTANT]
-> Developer PowerShell arguments -Arch and -HostArch are only available beginning with [Visual Studio 2022 version 17.1](/visualstudio/releases/2022/release-notes#1710--visual-studio-2022-version-171-newreleasebutton).
+> Developer PowerShell arguments `-Arch` and `-HostArch` are only available beginning with [Visual Studio 2022 version 17.1](/visualstudio/releases/2022/release-notes#1710--visual-studio-2022-version-171-newreleasebutton).
 
 The following table lists which architectures are supported, and whether they can be used for Target Architecture or Host Architecture arguments.
 
@@ -213,17 +206,20 @@ The following table lists which architectures are supported, and whether they ca
 
 #### Examples
 
-Start the Developer Command Prompt for Visual Studio 2019 Community Edition on a 64-bit machine, creating build outputs that target 64-bit:
+Start the Developer Command Prompt for Visual Studio 2019 Community Edition on a 64-bit machine, creating build outputs that target *64-bit*:
+
 ```cmd
 "%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\Common7\Tools\VsDevCmd.bat" -arch=amd64
 ```
 
-Start the Developer Command Prompt for Visual Studio 2019 Community Edition on a 64-bit machine, creating build outputs that target arm:
+Start the Developer Command Prompt for Visual Studio 2019 Community Edition on a 64-bit machine, creating build outputs that target *ARM*:
+
 ```cmd
 "%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\Common7\Tools\VsDevCmd.bat" -arch=arm -host_arch=amd64
 ```
 
-Start the Developer PowerShell for the Community Edition of [Visual Studio 2022 version 17.1](/visualstudio/releases/2022/release-notes#1710--visual-studio-2022-version-171-newreleasebutton) or later on a 64-bit machine, creating build outputs that target arm64:
+Start the Developer PowerShell for the Community Edition of [Visual Studio 2022 version 17.1](/visualstudio/releases/2022/release-notes#1710--visual-studio-2022-version-171-newreleasebutton) or later on a 64-bit machine, creating build outputs that target *ARM64*:
+
 ```powershell
 & 'C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\Tools\Launch-VsDevShell.ps1' -Arch arm64 -HostArch amd64
 ```
@@ -245,6 +241,6 @@ The Project Location can be adjusted in **Tools** > **Options** > **Projects &am
 
 ## Related content
 
-- [Windows Terminal](/windows/terminal/)
-- [.NET Framework Tools](/dotnet/framework/tools/index)
+- [What is Windows Terminal?](/windows/terminal/)
+- [.NET Framework tools](/dotnet/framework/tools/index)
 - [Use the Microsoft C++ toolset from the command line](/cpp/build/building-on-the-command-line)