forked from osmocom/wireshark
Update VS command prompt menu names for VS 2017.
At least on my W10 machine, they shols up as "xxx Native Tools Commmand Prompt for VS 2017", not "VS2017 xxx Native Tools Command Prompt". Change-Id: I55d7ad24df717cfce21f6abdaf97ed1972128e3c Reviewed-on: https://code.wireshark.org/review/30215 Reviewed-by: Guy Harris <guy@alum.mit.edu>
This commit is contained in:
parent
d2879a61bd
commit
b0759a02bb
|
@ -365,13 +365,13 @@ Make sure your repository path doesn't contain spaces.
|
|||
==== Open a Visual Studio Command Prompt
|
||||
|
||||
From the Start Menu (or Start Screen), navigate to the `Visual Studio
|
||||
2017' folder and choose the Command Prompt appropriate for
|
||||
the build you wish to make, e.g. `VS2017 x64 Native Tools Command
|
||||
Prompt' for a 64-bit version or `VS2017 x86 Native Tools Command Prompt'
|
||||
for a 32-bit version. Depending on your version of Windows the Command
|
||||
Prompt list might be directly under `Visual Studio 2017' or you might
|
||||
have to dig for it under multiple folders, e.g. `Visual Studio 2017 ->
|
||||
Visual Studio Tools -> Windows Desktop Command Prompts'.
|
||||
2017' folder and choose the Command Prompt appropriate for the build you
|
||||
wish to make, e.g. `x64 Native Tools Command Prompt for VS 2017' for a
|
||||
64-bit version or `x86 Native Tools Command Prompt for VS 2017' for a
|
||||
32-bit version. Depending on your version of Windows the Command Prompt
|
||||
list might be directly under `Visual Studio 2017' or you might have to
|
||||
dig for it under multiple folders, e.g. `Visual Studio 2017 -> Visual
|
||||
Studio Tools -> Windows Desktop Command Prompts'.
|
||||
|
||||
[TIP]
|
||||
.Pin the items to the Task Bar
|
||||
|
|
Loading…
Reference in New Issue