Check the documentation for the individual tools to determine which version of the command prompt you should use.

If you have other SDKs installed, such as the Windows 10 SDK or previous versions, you may see additional command prompts. (If you're running Visual Studio 2022, look for the same items that include '2022' instead of '2019'.) Select Visual Studio 2019 > Visual Studio Tools > Developer Command Prompt for VS 2019 or Developer PowerShell for VS 2019. Select Start and then expand All Programs. If you're running Visual Studio 2022, select Developer Command Prompt for VS 2022 or Developer PowerShell for VS 2022. If you're running Visual Studio 2019, select either Developer Command Prompt for VS 2019 or Developer PowerShell for VS 2019. This brings up a list that includes all installed Visual Studio command prompts. On the Start screen, press Ctrl+ Tab to open the Apps list, and then press V. Go to the Start screen, by pressing the Windows logo key on your keyboard for example. If you're running Visual Studio 2022, select either Developer Command Prompt for VS 2022 or Developer PowerShell for VS 2022.Īlternatively, you can start typing the name of the shell in the search box on the taskbar, and select the result you want as the result list starts to display the search matches. Select Start, and then scroll to the letter V.Įxpand the Visual Studio 2019 or Visual Studio 2022 folder. Select the App result that's associated with your search text. , and then in the Type here to search dialog box, enter either developer command prompt or developer powershell. You may have multiple command prompts, depending on the version of Visual Studio and any additional SDKs and workloads you've installed. On the menu bar, select Tools > Command Line > Developer Command Prompt or Developer PowerShell.Īnother way to start the shells is from the Start menu. Popular commandsįollow these steps to open Developer Command Prompt or Developer PowerShell from within Visual Studio: After opening one of these shells, you can enter the commands for different utilities without having to know where they're located. This behavior makes it convenient to run commands against the solution or its projects.īoth shells have specific environment variables set that enable you to use command-line developer tools more easily. When you open one of the developer shells from Visual Studio, either as a separate app or in the Terminal window, it opens to the directory of your current solution (if you have a solution loaded).

Dxwnd command line