differentiate terminal from shells

Author: gewarren

docs/framework/app-domains/how-to-view-the-contents-of-the-gac.md

@@ -19,7 +19,7 @@ Use the [global assembly cache tool (gacutil.exe)](../tools/gacutil-exe-gac-tool
 
 ## View the assemblies in the GAC
 
-To view a list of the assemblies in the global assembly cache, open a [command-line shell for developers](../tools/developer-command-prompt-for-vs.md)), and then enter the following command:
+To view a list of the assemblies in the global assembly cache, open a [command-line shell for developers](../tools/developer-command-prompt-for-vs.md), and then enter the following command:
 
 ```shell
 gacutil -l

docs/framework/app-domains/install-assembly-into-gac.md

@@ -40,7 +40,7 @@ gacutil -i <assembly name>
 
 In this command, *\<assembly name>* is the name of the assembly to install in the global assembly cache.
 
-If *gacutil.exe* isn't in your system path, use a [command-line shell for developers](../tools/developer-command-prompt-for-vs.md)).
+If *gacutil.exe* isn't in your system path, use a [command-line shell for developers](../tools/developer-command-prompt-for-vs.md).
 
 The following example installs an assembly with the file name *hello.dll* into the global assembly cache.
 

docs/framework/migration-guide/how-to-determine-which-versions-are-installed.md

@@ -202,7 +202,7 @@ The .NET Framework CLR installed with .NET Framework is versioned separately. Th
 
 - **The Clrver.exe tool**
 
-  Use the [CLR Version tool (Clrver.exe)](../tools/clrver-exe-clr-version-tool.md) to determine which versions of the CLR are installed on a computer. Open a [command-line shell for developers](../tools/developer-command-prompt-for-vs.md)) and enter `clrver`.
+  Use the [CLR Version tool (Clrver.exe)](../tools/clrver-exe-clr-version-tool.md) to determine which versions of the CLR are installed on a computer. Open a [command-line shell for developers](../tools/developer-command-prompt-for-vs.md) and enter `clrver`.
 
   Sample output:
 

docs/framework/tools/developer-command-prompt-for-vs.md

@@ -10,16 +10,16 @@ helpviewer_keywords:
   - "developer PowerShell"
   - "Visual Studio terminal"
 ms.assetid: 94fcf524-9045-4993-bfb2-e2d8bad44219
+no-loc: cmdlet
 ---
 # Command-line shells for developers
 
-Visual Studio 2019 includes three command-line shells for developers:
+Visual Studio 2019 includes two command-line shells for developers:
 
-- Developer Command Prompt for Visual Studio
-- Developer PowerShell
-- Visual Studio terminal
+- **Developer Command Prompt for Visual Studio** - A standard command prompt with certain environment variables set to make using command-line developer tools easier.
+- **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.
 
-All three of these tools have specific environment variables set that enable you to use command-line developer tools more easily. After opening one of these windows, you can enter the commands for different utilities without having to know where they're located. The commands you can run include:
+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. The commands you can run include:
 
 - [`MSBuild`](/visualstudio/msbuild/msbuild-command-line-reference), to build a project or solution.
 - [.NET Framework tools](index.md), such as [`clrver`](clrver-exe-clr-version-tool.md) and [`ildasm`](ildasm-exe-il-disassembler.md).
@@ -29,39 +29,39 @@ All three of these tools have specific environment variables set that enable you
 
 :::image type="content" source="media/developer-command-prompt-for-vs/command-prompt.png" alt-text="Developer Command Prompt for Visual Studio showing clrver tool":::
 
-When you open one of these windows from Visual Studio, 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.
+Starting in Visual Studio 2019 version 16.5, 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, choose **View** > **Terminal**.
 
-## Prerequisites
+:::image type="content" source="media/developer-command-prompt-for-vs/vs-terminal.png" alt-text="Visual Studio terminal showing multiple tabs":::
 
-- [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019)
+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.
 
-## Developer Command Prompt
+## Prerequisites
 
-There are a few ways you can open Developer Command Prompt for Visual Studio, including from Visual Studio, from the Windows Start menu, or by running the command to start Developer Command Prompt for Visual Studio.
+- [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019)
 
-### Start the command prompt from inside Visual Studio
+## Start the shell from inside Visual Studio
 
-Follow these steps to open Developer Command Prompt from within Visual Studio:
+Follow these steps to open Developer Command Prompt or Developer PowerShell from within Visual Studio:
 
 1. Open Visual Studio.
 
-1. On the menu bar, choose **Tools** > **Command Line** > **Developer Command Prompt**.
+1. On the menu bar, choose **Tools** > **Command Line** > **Developer Command Prompt** or **Developer PowerShell**.
 
    ![Command prompt menu item in Visual Studio](./media/developer-command-prompt-for-vs/vs-menu.png)
 
-### Search for the command prompt on your machine
+### Use the Windows Start menu
 
-You may have multiple command prompts, depending on the version of Visual Studio and any additional SDKs and workloads you've installed. If the following steps don't work, you can try to [manually locate the files on your machine](#manually-locate-the-files-on-your-machine) or [start the command prompt from inside Visual Studio](#start-the-command-prompt-from-inside-visual-studio).
+You may have multiple command prompts, depending on the version of Visual Studio and any additional SDKs and workloads you've installed. If the following steps don't work, you can try to [manually locate the files on your machine](#manually-locate-the-files-on-your-machine) or [start the shell from inside Visual Studio](#start-the-shell-from-inside-visual-studio).
 
 #### Windows 10
 
 1. Select **Start** ![Windows logo key on the keyboard.](./media/developer-command-prompt-for-vs/windows-logo-key-graphic.png) and scroll to the letter **V**.
 
 1. Expand the **Visual Studio 2019** folder.
 
-1. Choose **Developer Command Prompt for VS 2019** (or the command prompt you want to use).
+1. Choose **Developer Command Prompt for VS 2019** or **Developer PowerShell for VS 2019**.
 
-   Alternatively, you can start typing the name of the command prompt in the search box on the taskbar, and choose the result you want as the result list starts to display the search matches.
+   Alternatively, you can start typing the name of the shell in the search box on the taskbar, and choose the result you want as the result list starts to display the search matches.
 
    ![Animated gif showing the search behavior on Windows 10](./media/developer-command-prompt-for-vs/windows10-search.gif)
 
@@ -71,47 +71,65 @@ You may have multiple command prompts, depending on the version of Visual Studio
 
 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. Choose **Developer Command Prompt for VS 2019** (or the command prompt you want to use).
+1. Choose **Developer Command Prompt for VS 2019** or **Developer PowerShell for VS 2019**.
 
 #### Windows 7
 
 1. Choose **Start** and then expand **All Programs**.
 
-1. Choose **Visual Studio 2019** > **Visual Studio Tools** > **Developer Command Prompt for VS 2019**, or the command prompt you want to use.
+1. Choose **Visual Studio 2019** > **Visual Studio Tools** > **Developer Command Prompt for VS 2019** or **Developer PowerShell for VS 2019**.
 
    ![Windows 7 Start menu with the command prompt highlighted](./media/developer-command-prompt-for-vs/windows7-menu.png)
 
 If you have other SDKs installed, such as the [Windows 10 SDK](https://developer.microsoft.com/windows/downloads/windows-10-sdk) or [previous versions](https://developer.microsoft.com/windows/downloads/sdk-archive), you may see additional command prompts. Check the documentation for the individual tools to determine which version of the command prompt you should use.
 
 ### Manually locate the file
 
-Usually, the shortcuts for the command prompts 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 shortcut on your machine. Search for the name of the command prompt file, which is *VsDevCmd.bat*, or go to the Tools folder, such as *%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\Common7\Tools* (path changes according to your Visual Studio version, edition, and installation location).
+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.
 
-Once you've located the command prompt file, open it using the following commands in a regular command prompt window (but change the directory to match your installation of Visual Studio):
+#### 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(x86)%\Microsoft Visual Studio\2019\Community\Common7\Tools* (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:
 
 ```cmd
-cd %ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\Common7\Tools
-VsDevCmd.bat
+"%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\Common7\Tools\VsDevCmd.bat"
 ```
 
-Or enter the following command from the Windows **Run** dialog box:
+Or enter the following command in the Windows **Run** dialog box:
 
 ```cmd
 %comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\VsDevCmd.bat"
 ```
 
-## Developer PowerShell
+> [!TIP]
+> You'll need to edit the path to match your Visual Studio installation.
+
+#### Developer PowerShell
 
-To open [Developer PowerShell](https://devblogs.microsoft.com/visualstudio/the-powershell-you-know-and-love-now-with-a-side-of-visual-studio/), choose **Tools** > **Command Line** > **Developer PowerShell** from the menu bar.
+Search for a file named *Microsoft.VisualStudio.DevShell.dll*, or go to the Tools folder for Visual Studio, such as *%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\Common7\Tools* (path changes according to your Visual Studio version, edition, and installation location).
 
-## Visual Studio Terminal
+Once you've located the Developer PowerShell assembly file, open it by entering the following command in a PowerShell window:
+
+```powershell
+Import-Module 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\Microsoft.VisualStudio.DevShell.dll'; Enter-VsDevShell 0449c295
+```
+
+Or enter the following command in the Windows **Run** dialog box:
+
+```cmd
+powershell -noexit -command "& { Import-Module 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\Microsoft.VisualStudio.DevShell.dll'; Enter-VsDevShell 0449c295 }"
+```
 
-To open the integrated [Terminal](https://devblogs.microsoft.com/visualstudio/say-hello-to-the-new-visual-studio-terminal/) in Visual Studio, choose **View** > **Terminal** from the menu bar.
+> [!TIP]
+> You'll need to edit the path and instance ID (the final number) to match your Visual Studio installation. You can get the information from the *Target* value in the properties of the Developer PowerShell shortcut, which is located in the *%ProgramData%\Microsoft\Windows\Start Menu\Programs\Visual Studio 2019\Visual Studio Tools* folder.
 
 ## See also
 
 - [Developer PowerShell](https://devblogs.microsoft.com/visualstudio/the-powershell-you-know-and-love-now-with-a-side-of-visual-studio/)
 - [Say hello to the new Visual Studio terminal](https://devblogs.microsoft.com/visualstudio/say-hello-to-the-new-visual-studio-terminal/)
+- [Windows Terminal](/windows/terminal/)
 - [.NET Framework Tools](index.md)
 - [Manage external tools](/visualstudio/ide/managing-external-tools)
 - [Use the Microsoft C++ toolset from the command line](/cpp/build/building-on-the-command-line)