Skip to content

Commit 0adb449

Browse files
author
Colin Robertson
committed
More version distinctions
1 parent e86d4aa commit 0adb449

File tree

1 file changed

+18
-2
lines changed

1 file changed

+18
-2
lines changed

docs/build/building-on-the-command-line.md

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,22 @@ The command prompt shortcuts are installed in a version-specific Visual Studio f
3030
- **x86_x64 Cross Tools Command Prompt** - Sets the environment to use 32-bit, x86-native tools to build 64-bit, x64-native code.
3131
- **x64_x86 Cross Tools Command Prompt** - Sets the environment to use 64-bit, x64-native tools to build 32-bit, x86-native code.
3232

33+
::: moniker range=">= vs-2019"
34+
3335
The Start menu folder and shortcut names vary depending on the installed version of Visual Studio. If you set one, they also depend on the installation **Nickname**. For example, suppose you installed Visual Studio 2019, and you gave it a nickname of *Latest*. The developer command prompt shortcut is named **Developer Command Prompt for VS 2019 (Latest)**, in a folder named **Visual Studio 2019**.
3436

37+
::: moniker-end
38+
::: moniker range="= vs-2017"
39+
40+
The Start menu folder and shortcut names vary depending on the installed version of Visual Studio. If you set one, they also depend on the installation **Nickname**. For example, suppose you installed Visual Studio 2017, and you gave it a nickname of *Latest*. The developer command prompt shortcut is named **Developer Command Prompt for VS 2017 (Latest)**, in a folder named **Visual Studio 2017**.
41+
42+
::: moniker-end
43+
::: moniker range="< vs-2017"
44+
45+
The Start menu folder and shortcut names vary depending on the installed version of Visual Studio. For example, suppose you installed Visual Studio 2015. The developer command prompt shortcut is named **Developer Command Prompt for VS 2015**.
46+
47+
::: moniker-end
48+
3549
## <a name="developer_command_prompt"></a> To open a developer command prompt window
3650

3751
1. On the desktop, open the Windows **Start** menu, and then scroll to find and open the folder for your version of Visual Studio, for example, **Visual Studio 2019**.
@@ -127,15 +141,17 @@ Optionally specifies the Visual Studio compiler toolset to use. By default, the
127141

128142
Use **-vcvars_ver=14.2x.yyyyy** to specify a specific version of the Visual Studio 2019 compiler toolset.
129143

144+
Use **-vcvars_ver=14.16** to specify the latest version of the Visual Studio 2017 compiler toolset.
145+
130146
::: moniker-end
131147
::: moniker range="= vs-2017"
132148

149+
Use **-vcvars_ver=14.16** to specify the latest version of the Visual Studio 2017 compiler toolset.
150+
133151
Use **-vcvars_ver=14.1x.yyyyy** to specify a specific version of the Visual Studio 2017 compiler toolset.
134152

135153
::: moniker-end
136154

137-
Use **-vcvars_ver=14.16** to specify the latest version of the Visual Studio 2017 compiler toolset.
138-
139155
Use **-vcvars_ver=14.0** to specify the Visual Studio 2015 compiler toolset.
140156

141157
<a name="vcvarsall"></a>

0 commit comments

Comments
 (0)