dotnet · gewarren · Mar 5, 2021 · Feb 23, 2021 · Feb 23, 2021 · Feb 23, 2021
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -3767,6 +3767,11 @@
             "source_path": "docs/framework/security/wstrustchannelfactory-and-wstrustchannel.md",
             "redirect_url": "/previous-versions/dotnet/framework/security/wstrustchannelfactory-and-wstrustchannel"
         },
+        {
+            "source_path": "docs/framework/tools/developer-command-prompt-for-vs.md",
+            "redirect_url": "/visualstudio/ide/reference/command-prompt-powershell",
+            "redirect_document_id": true
+        },
         {
             "source_path": "docs/framework/ui-automation/ui-automation-specification-and-community-promise.md",
             "redirect_url": "/previous-versions/dotnet/netframework-4.0/bb986605(v=vs.100)"

diff --git a/docs/csharp/language-reference/compiler-messages/cs2032.md b/docs/csharp/language-reference/compiler-messages/cs2032.md
@@ -16,17 +16,17 @@ Character 'character' is not allowed on the command-line or in response files
 
  Compiler error CS2032 is difficult to demonstrate from the command line because the command line processor and the integrated development environment (IDE) filter out characters that are not valid. The following procedure generates the error by using a [response file](../compiler-options/response-file-compiler-option.md).
 
-### To generate this error
+## To generate this error
 
 1. In the *My Documents* folder, create a text file that is named *CS2032.rsp*, and then enter the following compiler options in it:
 
     ```console
     /target:exe /out:cs|2032.exe cs2032.cs
     ```
 
-2. In the *My Documents* folder, create a text file that is named *cs2032.cs* and that contains whatever you want.
+2. In the *My Documents* folder, create a text file that's named *cs2032.cs* and that contains whatever you want.
 
-3. Open the *Start* menu. Locate and select the [Developer Command Prompt for Visual Studio](../../../framework/tools/developer-command-prompt-for-vs.md).
+3. Open a [developer command-line shell](/visualstudio/ide/reference/command-prompt-powershell).
 
 4. Change the current directory to `C:\Users\\<YourUsername>\Documents`.
 

diff --git a/...sharp/language-reference/compiler-options/command-line-building-with-csc-exe.md b/...sharp/language-reference/compiler-options/command-line-building-with-csc-exe.md
@@ -11,9 +11,9 @@ ms.assetid: 66e70056-dd20-453c-a9b3-507e0478b015
 
 You can invoke the C# compiler by typing the name of its executable file (*csc.exe*) at a command prompt.
 
-If you use the **Developer Command Prompt for Visual Studio** window, all the necessary environment variables are set for you. For information on how to access this tool, see the [Developer Command Prompt for Visual Studio](../../../framework/tools/developer-command-prompt-for-vs.md) topic.
+If you use one of the command-line shells that Visual Studio installs, all the necessary environment variables are set for you. For information on how to access these shells, see [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell).
 
-If you use a standard Command Prompt window, you must adjust your path before you can invoke *csc.exe* from any subdirectory on your computer. You also must run *VsDevCmd.bat* to set the appropriate environment variables to support command-line builds. For more information about *VsDevCmd.bat*, including instructions for how to find and run it, see [How to set environment variables for the Visual Studio Command Line](./how-to-set-environment-variables-for-the-visual-studio-command-line.md).
+If you use a regular command prompt, you must adjust your path before you can invoke *csc.exe* from any subdirectory on your computer. You also must run *VsDevCmd.bat* to set the appropriate environment variables to support command-line builds. For more information about *VsDevCmd.bat*, including instructions for how to find and run it, see [How to set environment variables for the Visual Studio Command Line](./how-to-set-environment-variables-for-the-visual-studio-command-line.md).
 
 If you're working on a computer that has only the Windows Software Development Kit (SDK), you can use the C# compiler at the **SDK Command Prompt**, which you open from the **Microsoft .NET Framework SDK** menu option.
 
@@ -24,14 +24,6 @@ The *csc.exe* executable file usually is located in the Microsoft.NET\Framework\
 > [!TIP]
 > When you build a project by using the Visual Studio IDE, you can display the **csc** command and its associated compiler options in the **Output** window. To display this information, follow the instructions in [How to: View, Save, and Configure Build Log Files](/visualstudio/ide/how-to-view-save-and-configure-build-log-files#to-change-the-amount-of-information-included-in-the-build-log) to change the verbosity level of the log data to **Normal** or **Detailed**. After you rebuild your project, search the **Output** window for **csc** to find the invocation of the C# compiler.
 
- **In this topic**
-
-- [Rules for command-line syntax](#rules-for-command-line-syntax-for-the-c-compiler)
-
-- [Sample command lines](#sample-command-lines-for-the-c-compiler)
-
-- [Differences between C# compiler and C++ compiler output](#differences-between-c-compiler-and-c-compiler-output)
-
 ## Rules for command-line syntax for the C# compiler
 
 The C# compiler uses the following rules when it interprets arguments given on the operating system command line:

diff --git a/docs/csharp/language-reference/configure-language-version.md b/docs/csharp/language-reference/configure-language-version.md
@@ -83,7 +83,7 @@ The following table shows all current C# language versions. Your compiler may no
 [!INCLUDE [langversion-table](includes/langversion-table.md)]
 
 > [!TIP]
-> Open [Developer Command Prompt for Visual Studio](../../framework/tools/developer-command-prompt-for-vs.md), and run the following command to see the listing of language versions available on your machine.
+> Open a [developer command-line shell](/visualstudio/ide/reference/command-prompt-powershell), and run the following command to see the listing of language versions available on your machine.
 >
 > ```CMD
 > csc -langversion:?

diff --git a/docs/framework/app-domains/how-to-view-the-contents-of-the-gac.md b/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 [Developer Command Prompt for Visual Studio](../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](/visualstudio/ide/reference/command-prompt-powershell), and then enter the following command:
 
 ```shell
 gacutil -l
@@ -32,7 +32,7 @@ gacutil /l
 ```
 
 > [!NOTE]
-> In earlier versions of the .NET Framework, the [Shfusion.dll](/previous-versions/dotnet/netframework-4.0/34149zk3(v=vs.100)) Windows shell extension enabled you to view the global assembly cache in File Explorer. Beginning with the .NET Framework 4, Shfusion.dll is obsolete.
+> In earlier versions of .NET Framework, the [Shfusion.dll](/previous-versions/dotnet/netframework-4.0/34149zk3(v=vs.100)) Windows shell extension enabled you to view the global assembly cache in File Explorer. Beginning with .NET Framework 4, Shfusion.dll is obsolete.
 
 ## See also
 

diff --git a/docs/framework/app-domains/install-assembly-into-gac.md b/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 the [Developer command prompt for VS *\<version>*](../tools/developer-command-prompt-for-vs.md).
+If *gacutil.exe* isn't in your system path, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell).
 
 The following example installs an assembly with the file name *hello.dll* into the global assembly cache.
 
@@ -49,7 +49,7 @@ gacutil -i hello.dll
 ```
 
 > [!NOTE]
-> In earlier versions of the .NET Framework, the *Shfusion.dll* Windows shell extension let you install assemblies by dragging them to File Explorer. Beginning with .NET Framework 4, *Shfusion.dll* is obsolete.
+> In earlier versions of .NET Framework, the *Shfusion.dll* Windows shell extension let you install assemblies by dragging them to File Explorer. Beginning with .NET Framework 4, *Shfusion.dll* is obsolete.
 
 ## See also
 

diff --git a/docs/framework/migration-guide/how-to-determine-which-versions-are-installed.md b/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 the [Developer Command Prompt for Visual Studio](../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](/visualstudio/ide/reference/command-prompt-powershell) and enter `clrver`.
 
   Sample output:
 

diff --git a/docs/framework/toc.yml b/docs/framework/toc.yml
@@ -397,8 +397,6 @@ items:
     href: tools/certmgr-exe-certificate-manager-tool.md
   - name: Clrver.exe (CLR version tool)
     href: tools/clrver-exe-clr-version-tool.md
-  - name: Command prompts
-    href: tools/developer-command-prompt-for-vs.md
   - name: CorFlags.exe (CorFlags conversion tool)
     href: tools/corflags-exe-corflags-conversion-tool.md
   - name: Fuslogvw.exe (Assembly binding log viewer)

diff --git a/docs/framework/tools/al-exe-assembly-linker.md b/docs/framework/tools/al-exe-assembly-linker.md
@@ -16,7 +16,7 @@ The Assembly Linker generates a file that has an assembly manifest from one or m
 > [!NOTE]
 > Starting with Visual Studio 2008, both the C# and Visual Basic compilers automatically embed a Win32 manifest into the assembly. For more information, see [-win32manifest (C# Compiler Options)](../../csharp/language-reference/compiler-options/win32manifest-compiler-option.md).
 
-This tool is automatically installed with Visual Studio. To run the tool, use the Developer Command Prompt for Visual Studio (or the Visual Studio Command Prompt in Windows 7). For more information, see [Command Prompts](developer-command-prompt-for-vs.md).
+This tool is automatically installed with Visual Studio. To run the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell).
 
 At the command prompt, type the following:
 
@@ -172,4 +172,4 @@ al t2.netmodule /target:exe /out:t2a.exe /main:MyClass.Main
 - [*Sn.exe* (Strong Name Tool)](sn-exe-strong-name-tool.md)
 - [*Gacutil.exe* (Global Assembly Cache Tool)](gacutil-exe-gac-tool.md)
 - [Programming with Assemblies](../../standard/assembly/index.md)
-- [Command Prompts](developer-command-prompt-for-vs.md)
+- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell)
diff --git a/docs/framework/tools/aximp-exe-windows-forms-activex-control-importer.md b/docs/framework/tools/aximp-exe-windows-forms-activex-control-importer.md
@@ -18,7 +18,7 @@ The ActiveX Control Importer converts type definitions in a COM type library for
 
  To host the ActiveX control, you must generate a wrapper control that derives from <xref:System.Windows.Forms.AxHost>. This wrapper control contains an instance of the underlying ActiveX control. It knows how to communicate with the ActiveX control, but it appears as a Windows Forms control. This generated control hosts the ActiveX control and exposes its properties, methods, and events as those of the generated control.  
 
- This tool is automatically installed with Visual Studio. To run the tool, use the Developer Command Prompt for Visual Studio (or the Visual Studio Command Prompt in Windows 7). For more information, see [Command Prompts](developer-command-prompt-for-vs.md).  
+ This tool is automatically installed with Visual Studio. To run the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell).
 
  At the command prompt, type the following:  
 

diff --git a/docs/framework/tools/caspol-exe-code-access-security-policy-tool.md b/docs/framework/tools/caspol-exe-code-access-security-policy-tool.md
@@ -27,7 +27,7 @@ The Code Access Security (CAS) Policy tool (Caspol.exe) enables users and admini
 > [!NOTE]
 > 64-bit computers include both 64-bit and 32-bit versions of security policy. To ensure that your policy changes apply to both 32-bit and 64-bit applications, run both the 32-bit and 64-bit versions of Caspol.exe.  
 
- The Code Access Security Policy tool is automatically installed with the .NET Framework and with Visual Studio. You can find Caspol.exe in %windir%\Microsoft.NET\Framework\\*version* on 32-bit systems or %windir%\Microsoft.NET\Framework64\\*version* on 64-bit systems. (For example, the location is %windir%\Microsoft.NET\Framework64\v4.030319\caspol.exe for the .NET Framework 4 on a 64-bit system.) Multiple versions of the tool might be installed if your computer is running multiple versions of the .NET Framework side by side. You can run the tool from the installation directory. However, we recommend that you use the [Command Prompts](developer-command-prompt-for-vs.md), which does not require you to navigate to the installation folder.  
+ The Code Access Security Policy tool is automatically installed with .NET Framework and with Visual Studio. You can find Caspol.exe in %windir%\Microsoft.NET\Framework\\*version* on 32-bit systems or %windir%\Microsoft.NET\Framework64\\*version* on 64-bit systems. (For example, the location is %windir%\Microsoft.NET\Framework64\v4.030319\caspol.exe for .NET Framework 4 on a 64-bit system.) Multiple versions of the tool might be installed if your computer is running multiple versions of .NET Framework side by side. You can run the tool from the installation directory. However, we recommend that you use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell), which does not require you to navigate to the installation folder.  
 
  At the command prompt, type the following:  
 
@@ -249,4 +249,4 @@ caspol -all -resolveperm testassembly
 ## See also
 
 - [Tools](index.md)
-- [Command Prompts](developer-command-prompt-for-vs.md)
+- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell)
diff --git a/docs/framework/tools/cert2spc-exe-software-publisher-certificate-test-tool.md b/docs/framework/tools/cert2spc-exe-software-publisher-certificate-test-tool.md
@@ -14,7 +14,7 @@ ms.assetid: be434d7d-9c0d-46e7-8392-58a9b542d11d
 
 The Software Publisher Certificate Test tool creates a Software Publisher's Certificate (SPC) from one or more X.509 certificates. Cert2spc.exe is for test purposes only. You can obtain a valid SPC from a Certification Authority such as VeriSign or Thawte. For more information about creating X.509 certificates, see [Makecert.exe (Certificate Creation Tool)](/windows/desktop/SecCrypto/makecert).  
 
- This tool is automatically installed with Visual Studio. To run the tool, use the Developer Command Prompt for Visual Studio (or the Visual Studio Command Prompt in Windows 7). For more information, see [Command Prompts](developer-command-prompt-for-vs.md).  
+ This tool is automatically installed with Visual Studio. To run the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell).  
 
  At the command prompt, type the following:  
 
@@ -54,4 +54,4 @@ cert2spc oneCertificate.cer twoCertificate.cer mySPCFile.spc
 
 - [Tools](index.md)
 - [Makecert.exe (Certificate Creation Tool)](/windows/desktop/SecCrypto/makecert)
-- [Command Prompts](developer-command-prompt-for-vs.md)
+- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell)
diff --git a/docs/framework/tools/certmgr-exe-certificate-manager-tool.md b/docs/framework/tools/certmgr-exe-certificate-manager-tool.md
@@ -19,12 +19,12 @@ ms.assetid: 7e953b43-1374-4bbc-814f-53ca1b6b52bb
 
 The Certificate Manager tool (Certmgr.exe) manages certificates, certificate trust lists (CTLs), and certificate revocation lists (CRLs).  
 
- The Certificate Manager is automatically installed with Visual Studio. To start the tool, use the [Command Prompts](developer-command-prompt-for-vs.md).  
+ The Certificate Manager is automatically installed with Visual Studio. To start the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell).  
 
 > [!NOTE]
 > The Certificate Manager tool (Certmgr.exe) is a command-line utility, whereas Certificates (Certmgr.msc) is a Microsoft Management Console (MMC) snap-in. Because Certmgr.msc is usually found in the Windows System directory, entering `certmgr` at the command line may load the Certificates MMC snap-in even if you have opened the Developer Command Prompt for Visual Studio. This occurs because the path to the snap-in precedes the path to the Certificate Manager tool in the PATH environment variable. If you encounter this problem, you can execute Certmgr.exe commands by specifying the path to the executable.  
 
- This tool is automatically installed with Visual Studio. To run the tool, use the Developer Command Prompt for Visual Studio (or the Visual Studio Command Prompt in Windows 7). For more information, see [Command Prompts](developer-command-prompt-for-vs.md).  
+ This tool is automatically installed with Visual Studio. To run the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell).  
 
  For an overview of X.509 certificates, see [Working with Certificates](../wcf/feature-details/working-with-certificates.md).  
 
@@ -137,4 +137,4 @@ certmgr /put /c /s my newFile
 
 - [Tools](index.md)
 - [Makecert.exe (Certificate Creation Tool)](/windows/desktop/SecCrypto/makecert)
-- [Command Prompts](developer-command-prompt-for-vs.md)
+- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell)
diff --git a/docs/framework/tools/clrver-exe-clr-version-tool.md b/docs/framework/tools/clrver-exe-clr-version-tool.md
@@ -11,9 +11,9 @@ ms.assetid: cbc2ee86-bdc8-4a65-a8f1-ba23bce3a699
 
 The CLR Version tool (Clrver.exe) reports all the installed versions of the common language runtime (CLR) on the computer.  
 
- This tool is automatically installed with Visual Studio. To run the tool, use the Developer Command Prompt for Visual Studio (or the Visual Studio Command Prompt in Windows 7). For more information, see [Command Prompts](developer-command-prompt-for-vs.md).  
+ This tool is automatically installed with Visual Studio. To run the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell).  
 
- At the command prompt, type the following:  
+ At the command prompt, enter the following command:  
 
 ## Syntax  
 
@@ -55,4 +55,4 @@ clrver [option]
 ## See also
 
 - [Tools](index.md)
-- [Command Prompts](developer-command-prompt-for-vs.md)
+- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell)
diff --git a/docs/framework/tools/corflags-exe-corflags-conversion-tool.md b/docs/framework/tools/corflags-exe-corflags-conversion-tool.md
@@ -12,7 +12,7 @@ ms.assetid: ef900f8f-71ca-4dde-9b8c-95ddb0d7d89c
 
 The CorFlags Conversion tool allows you to configure the CorFlags section of the header of a portable executable image.  
 
- This tool is automatically installed with Visual Studio. To run the tool, use the Developer Command Prompt for Visual Studio (or the Visual Studio Command Prompt in Windows 7). For more information, see [Command Prompts](developer-command-prompt-for-vs.md).  
+ This tool is automatically installed with Visual Studio. To run the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell).  
 
  At the command prompt, type the following:  
 
@@ -51,4 +51,4 @@ CorFlags.exe assembly [options]
 
 - [Tools](index.md)
 - [64-bit Applications](../64-bit-apps.md)
-- [Command Prompts](developer-command-prompt-for-vs.md)
+- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell)