diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 921e67335ca16..8daad2691ede8 100644 --- 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 index d3b59cb691d0e..ef70cd8aa6f65 100644 --- a/docs/csharp/language-reference/compiler-messages/cs2032.md +++ b/docs/csharp/language-reference/compiler-messages/cs2032.md @@ -16,7 +16,7 @@ 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: @@ -24,9 +24,9 @@ Character 'character' is not allowed on the command-line or in response files /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\\\Documents`. diff --git a/docs/csharp/language-reference/compiler-options/command-line-building-with-csc-exe.md b/docs/csharp/language-reference/compiler-options/command-line-building-with-csc-exe.md index 6074841bda3e1..189870cd52af8 100644 --- a/docs/csharp/language-reference/compiler-options/command-line-building-with-csc-exe.md +++ b/docs/csharp/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 index a7036a58166ce..4d5b8e44b175c 100644 --- 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 index 4e956c8871e31..76e7319a30894 100644 --- 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 index 79f1392b88558..3312feb9a0fbf 100644 --- 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 In this command, *\* 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 *\*](../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 index 99b975bce47cf..9f4011bd512dc 100644 --- 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 index 0487c60deb874..f93342145696d 100644 --- 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 index 93cd186bac82a..6fd65f6d39414 100644 --- 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 index 667bde1fb143c..ca6b1429115fe 100644 --- 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 . 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 index 8bf829851bcf4..1c20d84bc723f 100644 --- 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 index 9e39cd54c5a16..3741f4c9b84e5 100644 --- 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 index 7dc7dc6631db2..df4a0e23fb4ee 100644 --- 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 index 4678c0ab4cabf..f0d99efd69988 100644 --- 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 index 14c9d3986e52a..618b6450ee56e 100644 --- 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) diff --git a/docs/framework/tools/developer-command-prompt-for-vs.md b/docs/framework/tools/developer-command-prompt-for-vs.md deleted file mode 100644 index 7ebd666e38633..0000000000000 --- a/docs/framework/tools/developer-command-prompt-for-vs.md +++ /dev/null @@ -1,93 +0,0 @@ ---- -title: "Developer Command Prompt for Visual Studio" -description: Learn to use the Developer Command Prompt for Visual Studio, which lets you use .NET tools more easily. It automatically sets specific environment variables. -ms.date: 01/05/2020 -helpviewer_keywords: - - "command prompt, Windows SDK" - - "Visual Studio command prompt" - - "command prompt, Visual Studio" - - "SDK command prompt" - - "tools [.NET Framework], setting environment variables" - - "environment variables, setting for tools" - - "developer command prompt" -ms.assetid: 94fcf524-9045-4993-bfb2-e2d8bad44219 ---- -# Developer Command Prompt for Visual Studio - -Developer Command Prompt for Visual Studio enables you to use .NET Framework tools more easily. It's a command prompt that automatically sets specific environment variables. After opening Developer Command Prompt, you can enter the commands for [.NET Framework tools](index.md) such as `ildasm` or `clrver`. - -## Prerequisites - -- [Visual Studio 2019](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) - -## Search for the command prompt on your machine - -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). - -### 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). - - 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. - - ![Animated gif showing the search behavior on Windows 10](./media/developer-command-prompt-for-vs/windows10-search.gif) - -### Windows 8.1 - -1. Go to the **Start** screen, by pressing the Windows logo key ![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. Choose **Developer Command Prompt for VS 2019** (or the command prompt you want to use). - -### 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. - - ![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 files on your machine - -Usually, the shortcuts for the command prompts you have installed are placed at the **Start Menu** folder for Visual Studio, such as in *%ProgramData%\Microsoft\Windows\Start Menu\Programs\Visual Studio 2019\Visual Studio Tools*. But if, for some reason, searching for the command prompt doesn't produce the expected results, you can try to manually locate the shortcut on your machine. Try searching for the name of the command prompt file, such as *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). - -## Start the command prompt from inside Visual Studio - -For easier access, you can add Developer Command Prompt, or any other command prompt, to the Tools menu in Visual Studio. To make the tool available, add it to the external tools list. Here are the steps: - -1. Open Visual Studio. - -1. On the start window, choose **Continue without code**. - -1. On the menu bar, choose **Tools** > **External Tools**. - -1. On the **External Tools** dialog box, choose the **Add** button. A new entry appears. - -1. Enter a **Title** for your new menu item such as `Command Prompt`. - -1. In the **Command** field, specify the file you want to launch, such as `%comspec%` or `C:\Windows\System32\cmd.exe`. - -1. In the **Arguments** field, specify where to find the specific command prompt you want to use, such as `/k "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\VsDevCmd.bat"`. This command launches the Developer Command Prompt that's installed with Visual Studio 2019 Community. Change this value according to your Visual Studio version, edition, and installation location. - -1. In the **Initial directory** field, specify the directory in which the command prompt will start. Choose a value such as **Project Directory** by selecting the arrow next to the field. - -1. Choose the **OK** button. - - ![External Tools dialog with the field values filled out.](./media/developer-command-prompt-for-vs/add-external-tool.png) - - The new menu item is added, and you can access the command prompt from the Tools menu. - - ![Command prompt menu item in Visual Studio](./media/developer-command-prompt-for-vs/command-prompt-vs-menu.png) - -## See also - -- [.NET Framework Tools](index.md) -- [Managing External Tools](/visualstudio/ide/managing-external-tools) -- [Use the Microsoft C++ toolset from the command line](/cpp/build/building-on-the-command-line) diff --git a/docs/framework/tools/fuslogvw-exe-assembly-binding-log-viewer.md b/docs/framework/tools/fuslogvw-exe-assembly-binding-log-viewer.md index c024136a877c6..cc303cc0063c6 100644 --- a/docs/framework/tools/fuslogvw-exe-assembly-binding-log-viewer.md +++ b/docs/framework/tools/fuslogvw-exe-assembly-binding-log-viewer.md @@ -18,17 +18,30 @@ The Assembly Binding Log Viewer displays details for assembly binds. This inform > [!IMPORTANT] > You must run fuslogvw.exe with administrator privileges. -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) with administrator credentials. 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) with administrator credentials. -At the command prompt, type the following: +At the command prompt, enter the following command: ```console fuslogvw ``` -The viewer displays an entry for each failed assembly bind. For each failure, the viewer describes the application that initiated the bind; the assembly the bind is for, including name, version, culture and public key; and the date and time of the failure. +The viewer displays an entry for each failed assembly bind. For each failure, the viewer describes: -### To change the log location view +- the application that initiated the bind +- the assembly the bind is for, including name, version, culture and public key +- the date and time of the failure + +## How to... + +- [Change the log location view](#change-the-log-location-view) +- [View details about a specific failure](#view-details-about-a-specific-failure) +- [Delete entries](#delete-entries) +- [Refresh the user interface](#refresh-the-user-interface) +- [Change the log settings](#change-the-log-settings) +- [View the About dialog](#view-the-about-dialog) + +### Change the log location view 1. Select the **Default** option button to view bind failures for all application types. By default, log entries are stored in per-user directories on disk in the wininet cache. @@ -37,7 +50,7 @@ The viewer displays an entry for each failed assembly bind. For each failure, th > [!NOTE] > The default bind location is preferable to the custom bind location. The runtime stores the default bind location in the wininet cache, and therefore automatically cleans it out. If you specify a custom bind location, you are responsible for cleaning it out. -### To view details about a specific failure +### View details about a specific failure 1. Select the application name of the desired entry in the viewer. @@ -91,33 +104,35 @@ LOG: Attempting download of new URL file:///C:/Program Files/Microsoft.NET/Frame LOG: All probing URLs attempted and failed. ``` -### To delete a single entry from the log +### Delete entries + +To delete a single entry from the log: 1. Select an entry in the viewer. 2. Click the **Delete Entry** button. -### To delete all entries from the log +To delete all entries from the log: - Click the **Delete All** button. -### To refresh the user interface +### Refresh the user interface - Click the **Refresh** button. The viewer does not automatically detect new log entries while it is running. You must use the **Refresh** button to display them. -### To change the log settings +### Change the log settings -- Click the **Settings** button to open the **Log Settings** dialog. +Click the **Settings** button to open the **Log Settings** dialog. -### To view the About dialog +### View the About dialog -- Click the **About** button. +Click the **About** button. -## Binding Logs for Native Images +## Binding logs for native images By default, Fuslogvw.exe logs normal assembly bind requests. Alternatively, you can log assembly binds for native images that were created using the [Ngen.exe (Native Image Generator)](ngen-exe-native-image-generator.md). -#### To log assembly binds for native images +### Log assembly binds for native images - In the **Log Categories** group, select the **Native Images** option button. @@ -175,27 +190,27 @@ Rejecting native image because it failed the security check. The assembly's perm Discarding native image. ``` -## The Log Settings Dialog +## The Log Settings dialog You can use the **Log Settings** dialog to perform the following actions. -#### To disable logging +### To disable logging - Select the **Log disabled** option button. Note that this option is selected by default. -#### To log assembly binds in exceptions +### To log assembly binds in exceptions - Select the **Log in exception text** option button. Only the least detailed fusion log information is logged in exception text. To view full information, use one of the other settings. See the Important note regarding assemblies that are loaded as domain neutral. -#### To log assembly bind failures +### To log assembly bind failures - Select the **Log bind failures to disk** option button. See the Important note regarding assemblies that are loaded as domain neutral. -#### To log all assembly binds +### To log all assembly binds - Select the **Log all binds to disk** option button. @@ -204,7 +219,7 @@ You can use the **Log Settings** dialog to perform the following actions. > [!IMPORTANT] > When an assembly is loaded as domain neutral, for example by setting the property to or , turning on logging might leak memory in some cases. This can happen if a log entry is made when a domain-neutral module is loaded into an application domain, and later the application domain is unloaded. The log entry might not be released until the process ends. Some debuggers automatically turn on logging. -#### To enable a custom log path +### To enable a custom log path 1. Select the **Enable custom log path** option button. @@ -213,9 +228,9 @@ You can use the **Log Settings** dialog to perform the following actions. > [!NOTE] > The [Assembly Binding Log Viewer (Fuslogvw.exe)](fuslogvw-exe-assembly-binding-log-viewer.md) uses the Internet Explorer (IE) cache to store its binding log. Due to occasional corruption in the IE cache, the [Assembly Binding Log Viewer (Fuslogvw.exe)](fuslogvw-exe-assembly-binding-log-viewer.md) can sometimes stop showing new binding logs in the viewing window. As a result of this corruption, the .NET binding infrastructure (fusion) cannot write to or read from the binding log. (This issue is not encountered if you use a custom log path.) To fix the corruption and allow fusion to show binding logs again, clear the IE cache by deleting temporary internet files from within the IE Internet Options dialog. > -> If your unmanaged application hosts the common language runtime by implementing the `IHostAssemblyManager` and `IHostAssemblyStore` interfaces, log entries can't be stored in the wininet cache. To view log entries for custom hosts that implement these interfaces, you must specify an alternate log path. +> If your unmanaged application hosts the common language runtime by implementing the `IHostAssemblyManager` and `IHostAssemblyStore` interfaces, log entries can't be stored in the wininet cache. To view log entries for custom hosts that implement these interfaces, you must specify an alternate log path. -#### To enable logging for apps running in the Windows app container +### To enable logging for apps running in the Windows app container 1. Enable a custom log path, as described in the previous procedure. By default, apps that are running in the Windows app container have limited access to the hard disk. The directory you specify will have read/write access for all apps in the app container. @@ -230,4 +245,4 @@ You can use the **Log Settings** dialog to perform the following actions. - [Tools](index.md) - [Global Assembly Cache](../app-domains/gac.md) - [How the Runtime Locates Assemblies](../deployment/how-the-runtime-locates-assemblies.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/gacutil-exe-gac-tool.md b/docs/framework/tools/gacutil-exe-gac-tool.md index 2ae229bcf6aff..041f5f93e9c9a 100644 --- a/docs/framework/tools/gacutil-exe-gac-tool.md +++ b/docs/framework/tools/gacutil-exe-gac-tool.md @@ -19,11 +19,11 @@ helpviewer_keywords: - "Global Assembly Cache tool" ms.assetid: 4c7be9c8-72ae-481f-a01c-1a4716806e99 --- -# Gacutil.exe (Global Assembly Cache Tool) +# Gacutil.exe (Global Assembly Cache tool) The Global Assembly Cache tool allows you to view and manipulate the contents of the global assembly cache and download cache. -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: @@ -176,4 +176,4 @@ gacutil /l - [Tools](index.md) - [Global Assembly Cache](../app-domains/gac.md) - [Regasm.exe (Assembly Registration Tool)](regasm-exe-assembly-registration-tool.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/ilasm-exe-il-assembler.md b/docs/framework/tools/ilasm-exe-il-assembler.md index acaa75d6cd024..a030d8b28b723 100644 --- a/docs/framework/tools/ilasm-exe-il-assembler.md +++ b/docs/framework/tools/ilasm-exe-il-assembler.md @@ -17,7 +17,7 @@ ms.assetid: 4ca3a4f0-4400-47ce-8936-8e219961c76f The IL Assembler generates a portable executable (PE) file from intermediate language (IL) assembly. (For more information on IL, see [Managed Execution Process](../../standard/managed-execution-process.md).) You can run the resulting executable, which contains IL and the required metadata, to determine whether the IL performs as expected. -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: @@ -225,4 +225,4 @@ The following IL code example corresponds to the previous C# code example. You c - [Tools](index.md) - [*Ildasm.exe* (IL Disassembler)](ildasm-exe-il-disassembler.md) - [Managed Execution Process](../../standard/managed-execution-process.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/ildasm-exe-il-disassembler.md b/docs/framework/tools/ildasm-exe-il-disassembler.md index 159c013396c69..a985eb5323cd8 100644 --- a/docs/framework/tools/ildasm-exe-il-disassembler.md +++ b/docs/framework/tools/ildasm-exe-il-disassembler.md @@ -15,7 +15,7 @@ ms.assetid: db27f6b2-f1ec-499e-be3a-7eecf95ca42b The IL Disassembler is a companion tool to the IL Assembler (*Ilasm.exe*). *Ildasm.exe* takes a portable executable (PE) file that contains intermediate language (IL) code and creates a text file suitable as input to *Ilasm.exe*. -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: @@ -182,4 +182,4 @@ A nested type must be preceded by its containing class, delimited by a forward s - [Tools](index.md) - [Ilasm.exe (IL Assembler)](ilasm-exe-il-assembler.md) - [Managed Execution Process](../../standard/managed-execution-process.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/index.md b/docs/framework/tools/index.md index 18604e96d4012..7c24698ef2987 100644 --- a/docs/framework/tools/index.md +++ b/docs/framework/tools/index.md @@ -1,7 +1,7 @@ --- -title: ".NET Framework Tools" +title: .NET Framework tools description: See a list of .NET tools that make it easier for you to create, deploy, and manage applications and components that target .NET. -ms.date: "03/30/2017" +ms.date: 03/30/2017 helpviewer_keywords: - "command line, .NET Framework tools" - ".NET Framework, tools" @@ -9,15 +9,15 @@ helpviewer_keywords: - "running .NET Framework tools" ms.assetid: a2ca532d-91f7-426a-9303-417c2ee1247c --- -# .NET Framework Tools +# .NET Framework tools The .NET Framework tools make it easier for you to create, deploy, and manage applications and components that target the .NET Framework. Most of the .NET Framework tools described in this section are automatically installed with Visual Studio. To download Visual Studio, visit the [Visual Studio Downloads](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=inline+link&utm_content=download+vs2019) page. -You can run all the tools from the command line with the exception of the Assembly Cache Viewer (*Shfusion.dll*). You must access *Shfusion.dll* from File Explorer. +You can run all the tools from the command line, with the exception of the Assembly Cache Viewer (*Shfusion.dll*). You must access *Shfusion.dll* from File Explorer. -The best way to run the command-line tools is by using the Developer Command Prompt for Visual Studio. These utilities enable you to run the tools easily, without navigating to the installation folder. For more information, see [Command Prompts](developer-command-prompt-for-vs.md). +The best way to run the command-line tools is by using one of the developer shells that Visual Studio installs. These utilities enable you to run the tools easily, without having to navigate to the installation folder. For more information, see [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell). > [!NOTE] > Some tools are specific to either 32-bit computers or 64-bit computers. Be sure to run the appropriate version of the tool for your computer. @@ -42,9 +42,6 @@ Manages certificates, certificate trust lists (CTLs), and certificate revocation - [Clrver.exe (CLR Version Tool)](clrver-exe-clr-version-tool.md) Reports all the installed versions of the common language runtime (CLR) on the computer. -- [Command Prompts](developer-command-prompt-for-vs.md) -Enables you to use .NET Framework tools more easily. It is a command prompt that automatically sets specific environment variables. - - [CorFlags.exe (CorFlags Conversion Tool)](corflags-exe-corflags-conversion-tool.md) Lets you configure the CorFlags section of the header of a portable executable (PE) image. diff --git a/docs/framework/tools/installutil-exe-installer-tool.md b/docs/framework/tools/installutil-exe-installer-tool.md index 0bb03983e2ab8..89fe2da3e8a40 100644 --- a/docs/framework/tools/installutil-exe-installer-tool.md +++ b/docs/framework/tools/installutil-exe-installer-tool.md @@ -20,7 +20,7 @@ ms.assetid: 3f9d0533-f895-4897-b4ea-528284e0241d The Installer tool is a command-line utility that allows you to install and uninstall server resources by executing the installer components in specified assemblies. This tool works in conjunction with classes in the namespace. -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: @@ -165,4 +165,4 @@ installutil /LogFile=myLog.InstallLog myAssembly.exe /LogFile=myTestLog.InstallL - - [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/lc-exe-license-compiler.md b/docs/framework/tools/lc-exe-license-compiler.md index 1d31181d6cb14..afb8c4591a571 100644 --- a/docs/framework/tools/lc-exe-license-compiler.md +++ b/docs/framework/tools/lc-exe-license-compiler.md @@ -22,7 +22,7 @@ The License Compiler reads text files that contain licensing information and pro Cross compilation between 32-bit and 64-bit is not supported when you use the License Compiler when building your project. This is because the License Compiler has to load assemblies, and loading 64-bit assemblies from a 32-bit application is not allowed, and vice versa. In this case, use the License Compiler from the command line to compile the license manually, and specify the corresponding architecture. - 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: @@ -93,4 +93,4 @@ lc @response.rsp - [Tools](index.md) - [Al.exe (Assembly Linker)](al-exe-assembly-linker.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/mage-exe-manifest-generation-and-editing-tool.md b/docs/framework/tools/mage-exe-manifest-generation-and-editing-tool.md index 747dd4c403410..902488038a7df 100644 --- a/docs/framework/tools/mage-exe-manifest-generation-and-editing-tool.md +++ b/docs/framework/tools/mage-exe-manifest-generation-and-editing-tool.md @@ -13,7 +13,7 @@ The Manifest Generation and Editing Tool (*Mage.exe*) is a command-line tool tha You can also use *MageUI.exe*, a graphical application, instead of *Mage.exe*. For more information, see [MageUI.exe (Manifest Generation and Editing Tool, Graphical Client)](mageui-exe-manifest-generation-and-editing-tool-graphical-client.md). -This tool is automatically installed with Visual Studio. To run the tool, use Developer Command Prompt for Visual Studio. 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). Two versions of *Mage.exe* and *MageUI.exe* are included with Visual Studio. To see version information, run *MageUI.exe*, select **Help**, and select **About**. This documentation describes version 4.0.x.x of *Mage.exe* and *MageUI.exe*. @@ -218,4 +218,4 @@ mage -Sign deploy.application -CertFile cert.pfx -KeyContainer keyfile.snk -Cryp - [Walkthrough: Manually Deploying a ClickOnce Application](/visualstudio/deployment/walkthrough-manually-deploying-a-clickonce-application) - [Trusted Application Deployment Overview](/visualstudio/deployment/trusted-application-deployment-overview) - [MageUI.exe (Manifest Generation and Editing Tool, Graphical Client)](mageui-exe-manifest-generation-and-editing-tool-graphical-client.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/mageui-exe-manifest-generation-and-editing-tool-graphical-client.md b/docs/framework/tools/mageui-exe-manifest-generation-and-editing-tool-graphical-client.md index ac6dc4e3e2308..45a28c6d69d9b 100644 --- a/docs/framework/tools/mageui-exe-manifest-generation-and-editing-tool-graphical-client.md +++ b/docs/framework/tools/mageui-exe-manifest-generation-and-editing-tool-graphical-client.md @@ -11,7 +11,7 @@ ms.assetid: f9e130a6-8117-49c4-839c-c988f641dc14 MageUI.exe supports the same functionality as the command-line tool Mage.exe, but with a Windows-based user interface (UI). With this tool you can create, edit, and sign deployment and application manifests. New manifests that are created with MageUI.exe target the .NET Framework 4 Client Profile. Previous versions of MageUI.exe should be used to target previous .NET Framework versions. When adding or removing assemblies from a manifest, or re-signing existing manifests, MageUI.exe does not update the manifest to target .NET Framework 4 Client Profile. For more information, see [Mage.exe (Manifest Generation and Editing Tool)](mage-exe-manifest-generation-and-editing-tool.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). Two versions of Mage.exe and MageUI.exe are included as a component of Visual Studio. To see version information, run MageUI.exe, select **Help**, and select **About**. This documentation describes version 4.0.x.x of Mage.exe and MageUI.exe. diff --git a/docs/framework/tools/mdbg-exe.md b/docs/framework/tools/mdbg-exe.md index 5727c914bfc46..3acb5d5be9fe1 100644 --- a/docs/framework/tools/mdbg-exe.md +++ b/docs/framework/tools/mdbg-exe.md @@ -103,4 +103,4 @@ mdbg> ## 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/media/developer-command-prompt-for-vs/add-external-tool.png b/docs/framework/tools/media/developer-command-prompt-for-vs/add-external-tool.png deleted file mode 100644 index 15c7545234b74..0000000000000 Binary files a/docs/framework/tools/media/developer-command-prompt-for-vs/add-external-tool.png and /dev/null differ diff --git a/docs/framework/tools/media/developer-command-prompt-for-vs/command-prompt-vs-menu.png b/docs/framework/tools/media/developer-command-prompt-for-vs/command-prompt-vs-menu.png deleted file mode 100644 index 0c79170c13507..0000000000000 Binary files a/docs/framework/tools/media/developer-command-prompt-for-vs/command-prompt-vs-menu.png and /dev/null differ diff --git a/docs/framework/tools/media/developer-command-prompt-for-vs/windows-logo-key-graphic.png b/docs/framework/tools/media/developer-command-prompt-for-vs/windows-logo-key-graphic.png deleted file mode 100644 index 29dba14a6b26f..0000000000000 Binary files a/docs/framework/tools/media/developer-command-prompt-for-vs/windows-logo-key-graphic.png and /dev/null differ diff --git a/docs/framework/tools/media/developer-command-prompt-for-vs/windows10-search.gif b/docs/framework/tools/media/developer-command-prompt-for-vs/windows10-search.gif deleted file mode 100644 index 68ffecb2034ad..0000000000000 Binary files a/docs/framework/tools/media/developer-command-prompt-for-vs/windows10-search.gif and /dev/null differ diff --git a/docs/framework/tools/media/developer-command-prompt-for-vs/windows7-menu.png b/docs/framework/tools/media/developer-command-prompt-for-vs/windows7-menu.png deleted file mode 100644 index f0fabc3cb35a7..0000000000000 Binary files a/docs/framework/tools/media/developer-command-prompt-for-vs/windows7-menu.png and /dev/null differ diff --git a/docs/framework/tools/mgmtclassgen-exe.md b/docs/framework/tools/mgmtclassgen-exe.md index f528976dab0ab..ae4ba6aac554b 100644 --- a/docs/framework/tools/mgmtclassgen-exe.md +++ b/docs/framework/tools/mgmtclassgen-exe.md @@ -152,4 +152,4 @@ public class App - - - [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/mpgo-exe-managed-profile-guided-optimization-tool.md b/docs/framework/tools/mpgo-exe-managed-profile-guided-optimization-tool.md index ad3a61589a8d0..cdd5ff8a33a57 100644 --- a/docs/framework/tools/mpgo-exe-managed-profile-guided-optimization-tool.md +++ b/docs/framework/tools/mpgo-exe-managed-profile-guided-optimization-tool.md @@ -18,7 +18,9 @@ Profile-guided optimization improves application startup time, memory utilizatio When you encounter performance issues with startup time and working set size for Intermediate Language (IL) assemblies, we recommend that you first use Ngen.exe to eliminate just-in-time (JIT) compilation costs and to facilitate code sharing. If you need additional improvements, you can then use Mpgo.exe to further optimize your application. You can use the performance data from the un-optimized native image assemblies as a baseline to evaluate the performance gains. Using Mpgo.exe may result in faster cold startup times and a smaller working set size. Mpgo.exe adds information to IL assemblies that Ngen.exe uses to create optimized native image assemblies. For more information, see the entry [Improving Launch Performance for your Desktop Applications](https://devblogs.microsoft.com/dotnet/improving-launch-performance-for-your-desktop-applications/) in the .NET blog. -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) with administrator credentials, and type the following at the command prompt. 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 [developer command-line shell](/visualstudio/ide/reference/command-prompt-powershell) with administrator credentials. + +Enter the following command at the command prompt: For desktop apps: @@ -28,8 +30,6 @@ mpgo –Scenario [-Import ] –AssemblyList -AppID -Timeout ``` @@ -127,6 +127,6 @@ mpgo.exe -import "C:\Optimized" -assemblylist "C:\MyApp\MyTax.dll" "C:\MyApp\MyT ## See also - [Ngen.exe (Native Image Generator)](ngen-exe-native-image-generator.md) -- [Command Prompts](developer-command-prompt-for-vs.md) +- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell) - [Improving Launch Performance for your Desktop Applications](https://devblogs.microsoft.com/dotnet/improving-launch-performance-for-your-desktop-applications/) - [An Overview of Performance Improvements in .NET Framework 4.5](/archive/msdn-magazine/2012/april/clr-an-overview-of-performance-improvements-in-net-4-5) diff --git a/docs/framework/tools/ngen-exe-native-image-generator.md b/docs/framework/tools/ngen-exe-native-image-generator.md index 2fd45fb67c58d..f40308e164881 100644 --- a/docs/framework/tools/ngen-exe-native-image-generator.md +++ b/docs/framework/tools/ngen-exe-native-image-generator.md @@ -52,7 +52,7 @@ For additional information on using Ngen.exe and the native image service, see [ > [!NOTE] > Ngen.exe syntax for versions 1.0 and 1.1 of the .NET Framework can be found in [Native Image Generator (Ngen.exe) Legacy Syntax](/previous-versions/dotnet/netframework-4.0/ms165073(v=vs.100)). -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: @@ -635,4 +635,4 @@ In the .NET Framework version 2.0, the only interaction with the native image se - [Tools](index.md) - [Managed Execution Process](../../standard/managed-execution-process.md) - [How the Runtime Locates Assemblies](../deployment/how-the-runtime-locates-assemblies.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/peverify-exe-peverify-tool.md b/docs/framework/tools/peverify-exe-peverify-tool.md index 36a36ff258a13..f106e868ef7e4 100644 --- a/docs/framework/tools/peverify-exe-peverify-tool.md +++ b/docs/framework/tools/peverify-exe-peverify-tool.md @@ -16,7 +16,7 @@ ms.assetid: f4f46f9e-8d08-4e66-a94b-0c69c9b0bbfa The PEVerify tool helps developers who generate Microsoft intermediate language (MSIL) (such as compiler writers and script engine developers) to determine whether their MSIL code and associated metadata meet type safety requirements. Some compilers generate verifiably type-safe code only if you avoid using certain language constructs. If you're using such a compiler, you may want to verify that you have not compromised the type safety of your code. You can run the PEVerify tool on your files to check the MSIL and metadata. - 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). ## Syntax @@ -119,4 +119,4 @@ peverify myAssembly.exe /break=100 /ignore@ignoreErrors.rsp - [Tools](index.md) - [Writing Verifiably Type-Safe Code](../misc/code-access-security-basics.md#typesafe_code) - [Type Safety and Security](../../standard/security/key-security-concepts.md#type-safety-and-security) -- [Command Prompts](developer-command-prompt-for-vs.md) +- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell) diff --git a/docs/framework/tools/regasm-exe-assembly-registration-tool.md b/docs/framework/tools/regasm-exe-assembly-registration-tool.md index 2c2a9bb80a465..4dedf09e5cb7b 100644 --- a/docs/framework/tools/regasm-exe-assembly-registration-tool.md +++ b/docs/framework/tools/regasm-exe-assembly-registration-tool.md @@ -13,7 +13,7 @@ ms.assetid: e190e342-36ef-4651-a0b4-0e8c2c0281cb The Assembly Registration tool reads the metadata within an assembly and adds the necessary entries to the registry, which allows COM clients to create .NET Framework classes transparently. Once a class is registered, any COM client can use it as though the class were a COM class. The class is registered only once, when the assembly is installed. Instances of classes within the assembly cannot be created from COM until they are actually registered. -To run the tool, use the Developer Command Prompt for Visual Studio. For more information, see [Command Prompts](developer-command-prompt-for-vs.md). +To run the tool, use a [developer command-line shell](/visualstudio/ide/reference/command-prompt-powershell). At the command prompt, type the following: @@ -83,4 +83,4 @@ regasm myTest.dll /tlb:myTest.tlb - [Tlbexp.exe (Type Library Exporter)](tlbexp-exe-type-library-exporter.md) - [Tlbimp.exe (Type Library Importer)](tlbimp-exe-type-library-importer.md) - [Registering Assemblies with COM](../interop/registering-assemblies-with-com.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/regsvcs-exe-net-services-installation-tool.md b/docs/framework/tools/regsvcs-exe-net-services-installation-tool.md index 0fb54387e94b0..2b56d70f68783 100644 --- a/docs/framework/tools/regsvcs-exe-net-services-installation-tool.md +++ b/docs/framework/tools/regsvcs-exe-net-services-installation-tool.md @@ -21,7 +21,7 @@ The .NET Services Installation tool performs the following actions: - Configures services that you have added programmatically to your class. - 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). + To run the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell). At the command prompt, type the following: @@ -86,4 +86,4 @@ regsvcs /appname:myTargetApp /tlb:newTest.tlb myTest.dll - [Tools](index.md) - [How to: Sign an Assembly with a Strong Name](../../standard/assembly/sign-strong-name.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/resgen-exe-resource-file-generator.md b/docs/framework/tools/resgen-exe-resource-file-generator.md index c637c69e51744..bc573e0a07e12 100644 --- a/docs/framework/tools/resgen-exe-resource-file-generator.md +++ b/docs/framework/tools/resgen-exe-resource-file-generator.md @@ -49,7 +49,7 @@ resgen /? If you use Resgen.exe to generate binary .resources files, you can use a language compiler to embed the binary files into executable assemblies, or you can use the [Assembly Linker (Al.exe)](al-exe-assembly-linker.md) to compile them into satellite assemblies. - 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: @@ -346,4 +346,4 @@ resgen StringResources.txt /str:vb,,StringResources - [Resources in Desktop Apps](../resources/index.md) - [Creating Resource Files](../resources/creating-resource-files-for-desktop-apps.md) - [Al.exe (Assembly Linker)](al-exe-assembly-linker.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/secannotate-exe-net-security-annotator-tool.md b/docs/framework/tools/secannotate-exe-net-security-annotator-tool.md index e148c0439e422..0691b11659b47 100644 --- a/docs/framework/tools/secannotate-exe-net-security-annotator-tool.md +++ b/docs/framework/tools/secannotate-exe-net-security-annotator-tool.md @@ -13,7 +13,7 @@ The .NET Security Annotator tool (SecAnnotate.exe) is a command-line application A Visual Studio extension, [Security Annotator](https://marketplace.visualstudio.com/items?itemName=sheldonb.SecurityAnnotator), provides a graphical user interface to SecAnnotate.exe and enables you to run the tool from Visual Studio. - 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, where *parameters* are described in the following section, and *assemblies* consist of one or more assembly names separated by blanks: diff --git a/docs/framework/tools/signtool-exe.md b/docs/framework/tools/signtool-exe.md index 8734371b87c7f..476778c5232c1 100644 --- a/docs/framework/tools/signtool-exe.md +++ b/docs/framework/tools/signtool-exe.md @@ -11,7 +11,7 @@ ms.assetid: 0c25ff6c-bff3-422e-b017-146a3ee86cb9 Sign Tool is a command-line tool that digitally signs files, verifies signatures in files, and time-stamps files. - 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). > [!Note] > The Windows 10 SDK, Windows 10 HLK, Windows 10 WDK and Windows 10 ADK **builds 20236 and later** require specifying the digest algorithm. The SignTool `sign` command requires the `/fd` **file digest algorithm** and the `/td` **timestamp digest algorithm** option to be specified during signing and timestamping, respectively. A warning (error code 0, initially) will be thrown if `/fd` is not specified during signing and if `/td` is not specified during timestamping. In later versions of SignTool, the warning will become an error. SHA256 is recommended and considered to be more secure than SHA1 by the industry. @@ -225,4 +225,4 @@ signtool verify /c MyCatalog.cat SystemFile.dll ## 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/sn-exe-strong-name-tool.md b/docs/framework/tools/sn-exe-strong-name-tool.md index 1640e1481f62a..277d951e386a7 100644 --- a/docs/framework/tools/sn-exe-strong-name-tool.md +++ b/docs/framework/tools/sn-exe-strong-name-tool.md @@ -21,7 +21,7 @@ The Strong Name tool (Sn.exe) helps sign assemblies with [strong names](../../st For more information on strong naming and strong-named assemblies, see [Strong-Named Assemblies](../../standard/assembly/strong-named.md) and [How to: Sign an Assembly with a Strong Name](../../standard/assembly/sign-strong-name.md). - The Strong Name tool is automatically installed with Visual Studio. To start the tool, use the Developer Command Prompt (or the Visual Studio Command Prompt in Windows 7). For more information, see [Command Prompts](developer-command-prompt-for-vs.md). + The Strong Name tool is automatically installed with Visual Studio. To start the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell). > [!NOTE] > On 64-bit computers, run the 32-bit version of Sn.exe by using the Developer Command Prompt for Visual Studio and the 64-bit version by using the Visual Studio x64 Win64 Command Prompt. @@ -125,4 +125,4 @@ sn -d MyContainer - [Tools](index.md) - [Al.exe (Assembly Linker)](al-exe-assembly-linker.md) - [Strong-Named Assemblies](../../standard/assembly/strong-named.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/sos-dll-sos-debugging-extension.md b/docs/framework/tools/sos-dll-sos-debugging-extension.md index ae3149f952cf0..35e1fcae103bd 100644 --- a/docs/framework/tools/sos-dll-sos-debugging-extension.md +++ b/docs/framework/tools/sos-dll-sos-debugging-extension.md @@ -201,4 +201,4 @@ The following command displays information about the metadata token at the addre ## 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/sqlmetal-exe-code-generation-tool.md b/docs/framework/tools/sqlmetal-exe-code-generation-tool.md index 09b4bf7487f94..788b822324733 100644 --- a/docs/framework/tools/sqlmetal-exe-code-generation-tool.md +++ b/docs/framework/tools/sqlmetal-exe-code-generation-tool.md @@ -21,15 +21,13 @@ The SqlMetal command-line tool generates code and mapping for the [!INCLUDE[vbte - From a .dbml file, generate code and mapping attributes or a mapping file. - This tool is automatically installed with Visual Studio. By default, the file is located at `drive`:\Program Files\Microsoft SDKs\Windows\v`n.nn`\bin. If you do not install Visual Studio, you can also get the SQLMetal file by downloading the [Windows SDK](https://go.microsoft.com/fwlink/?LinkId=142225). +This tool is automatically installed with Visual Studio. By default, the file is located at `drive`:\Program Files\Microsoft SDKs\Windows\v`n.nn`\bin. If you do not install Visual Studio, you can also get the SQLMetal file by downloading the [Windows SDK](https://go.microsoft.com/fwlink/?LinkId=142225). > [!NOTE] > Developers who use Visual Studio can also use the Object Relational Designer to generate entity classes. The command-line approach scales well for large databases. Because SqlMetal is a command-line tool, you can use it in a build process. - 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).At the command prompt, type the following: - -## Syntax - +To run the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell). At the command prompt, enter the following command: + ```console sqlmetal [options] [] ``` diff --git a/docs/framework/tools/storeadm-exe-isolated-storage-tool.md b/docs/framework/tools/storeadm-exe-isolated-storage-tool.md index db7a564809896..7949a64b87cc8 100644 --- a/docs/framework/tools/storeadm-exe-isolated-storage-tool.md +++ b/docs/framework/tools/storeadm-exe-isolated-storage-tool.md @@ -14,7 +14,7 @@ ms.assetid: b81202b8-d91d-4b23-9c53-4a112f74a44a The Isolated Storage tool lists or removes all existing stores for the current user. - 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: @@ -59,4 +59,4 @@ storeadm [/list][/machine][/remove][/roaming][/quiet] - [Tools](index.md) - [Isolated Storage](../../standard/io/isolated-storage.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/tlbexp-exe-type-library-exporter.md b/docs/framework/tools/tlbexp-exe-type-library-exporter.md index 118c931f618fc..aa19ccf244149 100644 --- a/docs/framework/tools/tlbexp-exe-type-library-exporter.md +++ b/docs/framework/tools/tlbexp-exe-type-library-exporter.md @@ -14,7 +14,7 @@ ms.assetid: a487d61b-d166-467b-a7ca-d8b52fbff42d The Type Library Exporter generates a type library that describes the types defined in a common language runtime assembly. - 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: @@ -132,4 +132,4 @@ tlbexp Sample.dll - [Regasm.exe (Assembly Registration Tool)](regasm-exe-assembly-registration-tool.md) - [Assembly to Type Library Conversion Summary](/previous-versions/dotnet/netframework-4.0/xk1120c3(v=vs.100)) - [Tlbimp.exe (Type Library Importer)](tlbimp-exe-type-library-importer.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/tlbimp-exe-type-library-importer.md b/docs/framework/tools/tlbimp-exe-type-library-importer.md index dfae2ac70f3cb..2d72de5bb47ed 100644 --- a/docs/framework/tools/tlbimp-exe-type-library-importer.md +++ b/docs/framework/tools/tlbimp-exe-type-library-importer.md @@ -16,7 +16,7 @@ ms.assetid: ec0a8d63-11b3-4acd-b398-da1e37e97382 The Type Library Importer converts the type definitions found within a COM type library into equivalent definitions in a common language runtime assembly. The output of Tlbimp.exe is a binary file (an assembly) that contains runtime metadata for the types defined within the original type library. You can examine this file with tools such as [Ildasm.exe](ildasm-exe-il-disassembler.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: @@ -133,4 +133,4 @@ void SomeMethod(out bool x); - [Sn.exe (Strong Name Tool)](sn-exe-strong-name-tool.md) - [Strong-Named Assemblies](../../standard/assembly/strong-named.md) - [Attributes for Importing Type Libraries into Interop Assemblies](/previous-versions/dotnet/netframework-4.0/y6a7ak23(v=vs.100)) -- [Command Prompts](developer-command-prompt-for-vs.md) +- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell) diff --git a/docs/framework/tools/winmdexp-exe-windows-runtime-metadata-export-tool.md b/docs/framework/tools/winmdexp-exe-windows-runtime-metadata-export-tool.md index 779686b8d7dde..f6e2c0594cf41 100644 --- a/docs/framework/tools/winmdexp-exe-windows-runtime-metadata-export-tool.md +++ b/docs/framework/tools/winmdexp-exe-windows-runtime-metadata-export-tool.md @@ -13,7 +13,7 @@ The Windows Runtime Metadata Export Tool (Winmdexp.exe) transforms a .NET Framew When you use the **Windows Runtime Component** template, which is located under **Windows Store** for C# and Visual Basic in Visual Studio 2013 or Visual Studio 2012, the compiler target is a .winmdobj file, and a subsequent build step calls Winmdexp.exe to export the .winmdobj file to a .winmd file. This is the recommended way to build a Windows Runtime component. Use Winmdexp.exe directly when you want more control over the build process than Visual Studio provides. - 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/winres-exe-windows-forms-resource-editor.md b/docs/framework/tools/winres-exe-windows-forms-resource-editor.md index 3f7fa870809e0..adf7bfed15bf5 100644 --- a/docs/framework/tools/winres-exe-windows-forms-resource-editor.md +++ b/docs/framework/tools/winres-exe-windows-forms-resource-editor.md @@ -17,7 +17,7 @@ ms.assetid: cb8bc835-9221-4888-af53-1a4f5fad6c48 The Windows Resource Localization Editor, Winres.exe, is a visual layout tool that helps localization experts localize Windows Forms user interface (UI) resources used by forms. The .resx or .resources files that are used as input to Winres.exe can be created using a visual design environment such as Microsoft Visual Studio. For information on deploying resources in .NET Framework applications, see [Resources in Desktop Apps](../resources/index.md). -Winres.exe is installed with Visual Studio. To run the tool, use the Developer Command Prompt for Visual Studio. For more information, see [Command Prompts](developer-command-prompt-for-vs.md). +Winres.exe is installed with Visual Studio. To run the tool, use a [command-line shell for developers](/visualstudio/ide/reference/command-prompt-powershell). ## Syntax diff --git a/docs/framework/wcf/feature-details/deploying-an-internet-information-services-hosted-wcf-service.md b/docs/framework/wcf/feature-details/deploying-an-internet-information-services-hosted-wcf-service.md index 105f78309f6fe..72f7d1226207c 100644 --- a/docs/framework/wcf/feature-details/deploying-an-internet-information-services-hosted-wcf-service.md +++ b/docs/framework/wcf/feature-details/deploying-an-internet-information-services-hosted-wcf-service.md @@ -28,11 +28,11 @@ WCF, IIS, and ASP.NET must be installed for IIS-hosted WCF services to function Instructions for installing IIS on other operating systems can be found at [Install IIS on Windows Vista and Windows 7](/iis/install/installing-iis-7/installing-iis-on-windows-vista-and-windows-7) and [Install IIS 8.5 on Windows Server 2012 R2](/iis/install/installing-iis-85/installing-iis-85-on-windows-server-2012-r2). -The installation process for .NET Framework automatically registers WCF with IIS if IIS is already present on the machine. If IIS is installed after the .NET Framework, an additional step is required to register WCF with IIS and ASP.NET. You can do this as follows, depending on your operating system: +The installation process for .NET Framework automatically registers WCF with IIS if IIS is already present on the machine. If IIS is installed after .NET Framework, an additional step is required to register WCF with IIS and ASP.NET. You can do this as follows, depending on your operating system: -- Windows 7 and Windows Server 2003: Use the [ServiceModel Registration Tool (ServiceModelReg.exe)](../servicemodelreg-exe.md) tool to register WCF with IIS. To use this tool, type **ServiceModelReg.exe /i /x** in the [Developer Command Prompt for Visual Studio](../../tools/developer-command-prompt-for-vs.md). +- Windows 7 and Windows Server 2003: Use the [ServiceModel Registration Tool (ServiceModelReg.exe)](../servicemodelreg-exe.md) tool to register WCF with IIS. To use this tool, enter `ServiceModelReg.exe /i /x` in a [developer command-line shell](/visualstudio/ide/reference/command-prompt-powershell). -- Windows 7: Finally, you must verify that ASP.NET is configured to use the .NET Framework version 4 or later. You do this by running the ASPNET_Regiis tool with the `–i` option. For more information, see [ASP.NET IIS Registration Tool](/previous-versions/dotnet/netframework-3.5/k6h9cz8h(v=vs.90)). +- Windows 7: Finally, you must verify that ASP.NET is configured to use .NET Framework version 4 or later. You do this by running the ASPNET_Regiis tool with the `–i` option. For more information, see [ASP.NET IIS Registration Tool](/previous-versions/dotnet/netframework-3.5/k6h9cz8h(v=vs.90)). ## Create a New IIS Application or Reuse an Existing ASP.NET Application diff --git a/docs/framework/windows-services/walkthrough-creating-a-windows-service-application-in-the-component-designer.md b/docs/framework/windows-services/walkthrough-creating-a-windows-service-application-in-the-component-designer.md index e0ff506b36d23..bcea4aaa69941 100644 --- a/docs/framework/windows-services/walkthrough-creating-a-windows-service-application-in-the-component-designer.md +++ b/docs/framework/windows-services/walkthrough-creating-a-windows-service-application-in-the-component-designer.md @@ -464,9 +464,9 @@ Each Windows service has a registry entry under the **HKEY_LOCAL_MACHINE\SYSTEM\ Now that you've built the Windows service, you can install it. To install a Windows service, you must have administrator credentials on the computer where it's installed. -1. Open [Developer Command Prompt for Visual Studio](../tools/developer-command-prompt-for-vs.md) with administrative credentials. From the Windows **Start** menu, select **Developer Command Prompt for VS 2017** in the Visual Studio folder, then select **More** > **Run as Administrator** from the shortcut menu. +1. Open [Developer Command Prompt for Visual Studio](/visualstudio/ide/reference/command-prompt-powershell) with administrative credentials. -2. In the **Developer Command Prompt for Visual Studio** window, navigate to the folder that contains your project's output (by default, the *\bin\Debug* subdirectory of your project). +2. In **Developer Command Prompt for Visual Studio**, navigate to the folder that contains your project's output (by default, the *\bin\Debug* subdirectory of your project). 3. Enter the following command: diff --git a/docs/standard/assembly/sign-strong-name.md b/docs/standard/assembly/sign-strong-name.md index 038136ef07744..3b3402b91f0c2 100644 --- a/docs/standard/assembly/sign-strong-name.md +++ b/docs/standard/assembly/sign-strong-name.md @@ -45,7 +45,7 @@ There are a number of ways to sign an assembly with a strong name: ### Create and sign an assembly with a strong name by using the Assembly Linker -At the [Developer Command Prompt for Visual Studio](../../framework/tools/developer-command-prompt-for-vs.md), enter the following command: +Open a [developer command-line shell](/visualstudio/ide/reference/command-prompt-powershell), and enter the following command: **al** **/out:**\<*assemblyName*> *\* **/keyfile:**\<*keyfileName*> diff --git a/docs/standard/serialization/xml-schema-definition-tool-xsd-exe.md b/docs/standard/serialization/xml-schema-definition-tool-xsd-exe.md index e58c48ff0e09a..902a5d9a8b226 100644 --- a/docs/standard/serialization/xml-schema-definition-tool-xsd-exe.md +++ b/docs/standard/serialization/xml-schema-definition-tool-xsd-exe.md @@ -230,7 +230,7 @@ xsd myAssembly.dll - - - [Tools](../../framework/tools/index.md) -- [Command Prompts](../../framework/tools/developer-command-prompt-for-vs.md) +- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell) - [LINQ to DataSet Overview](../../framework/data/adonet/linq-to-dataset-overview.md) - [Querying Typed DataSets](../../framework/data/adonet/querying-typed-datasets.md) - [LINQ (Language-Integrated Query) (C#)](../../csharp/programming-guide/concepts/linq/index.md) diff --git a/docs/standard/serialization/xml-serializer-generator-tool-sgen-exe.md b/docs/standard/serialization/xml-serializer-generator-tool-sgen-exe.md index 6e4c749b68dcb..67c0e9b98ce83 100644 --- a/docs/standard/serialization/xml-serializer-generator-tool-sgen-exe.md +++ b/docs/standard/serialization/xml-serializer-generator-tool-sgen-exe.md @@ -61,4 +61,4 @@ sgen Data.dll ## See also - [Tools](../../framework/tools/index.md) -- [Command Prompts](../../framework/tools/developer-command-prompt-for-vs.md) +- [Developer command-line shells](/visualstudio/ide/reference/command-prompt-powershell) diff --git a/docs/visual-basic/language-reference/error-messages/unable-to-emit-assembly-error-message.md b/docs/visual-basic/language-reference/error-messages/unable-to-emit-assembly-error-message.md index 4c70457c8914c..0c4eb8594c5f2 100644 --- a/docs/visual-basic/language-reference/error-messages/unable-to-emit-assembly-error-message.md +++ b/docs/visual-basic/language-reference/error-messages/unable-to-emit-assembly-error-message.md @@ -31,7 +31,7 @@ The Visual Basic compiler calls the Assembly Linker (*Al.exe*, also known as Ali 2. Delete the COM reference that is generating the error from your project. -3. Open 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 directory to the directory where you want to place your assembly wrapper.