Skip to content

Commit fda28bb

Browse files
author
mikeblome
committed
updated all references to VS 2017 in the build folder
1 parent 2c85063 commit fda28bb

27 files changed

+91
-62
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Use the MSVC toolset from the command line - Visual Studio"
33
description: "Use the Microsoft C++ compiler toolchain (MSVC) from the command line outside of the Visual Studio IDE."
44
ms.custom: "conceptual"
5-
ms.date: "04/25/2019"
5+
ms.date: "05/16/2019"
66
helpviewer_keywords: ["command-line builds [C++]", "compiling source code [C++], command line", "builds [C++], command-line", "command line [C++], building from", "command line [C++], compilers"]
77
ms.assetid: 7ca9daed-a003-4162-842d-908f79058365
88
---

‎docs/build/cmakesettings-reference.md‎

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
title: "CMakeSettings.json schema reference"
3-
ms.date: "04/25/2019"
3+
ms.date: "05/16/2019"
44
helpviewer_keywords: ["CMake in Visual C++"]
55
ms.assetid: 444d50df-215e-4d31-933a-b41841f186f8
66
---
77
# CMakeSettings.json schema reference
88

9-
The **cmakesettings.json**` file contains information that specifies how Visual Studio should interact with CMake to build a project for a specified platform. The file stores information such as environment variables or arguments for the cmake.exe environment. You can edit directly or use the **CMake Settings editor**. See [Customize CMake build settings in Visual Studio](customize-cmake-settings.md) for more information about the editor.
9+
The **cmakesettings.json**` file contains information that specifies how Visual Studio should interact with CMake to build a project for a specified platform. The file stores information such as environment variables or arguments for the cmake.exe environment. You can edit directly or use the **CMake Settings editor** (Visuasl Studio 2019 and later). See [Customize CMake build settings in Visual Studio](customize-cmake-settings.md) for more information about the editor.
1010

1111
## Environments
1212

@@ -21,7 +21,7 @@ The `environments` array contains a list of `items` of type `object` which defin
2121
"inheritEnvironments": [ "msvc_x64_x64" ]
2222
```
2323

24-
The example above is the same as running the **Developer Command Prompt for VS 2017** with the **-arch=amd64 -host_arch=amd64** arguments. Any custom environment can be used, or these predefined environments:
24+
The example above is the same as running the **Developer Command Prompt for VS 2017** or **Developer Command Prompt for VS 2019** with the **-arch=amd64 -host_arch=amd64** arguments. Any custom environment can be used, or these predefined environments:
2525

2626
- linux_arm: Target ARM Linux remotely.
2727
- linux_x64: Target x64 Linux remotely.
@@ -43,7 +43,13 @@ A `configuration` has these properties:
4343
- `name`: names the configuration.
4444
- `description`: description of this configuration that will appear in menus.
4545
- `generator`: specifies CMake generator to use for this configuration. May be one of:
46+
47+
**Visual Studio 2019 only:**
48+
- Visual Studio 16 2019
49+
- Visual Studio 16 2019 Win64
50+
- Visual Studio 16 2019 ARM
4651

52+
**Visual Studio 2017 and later:**
4753
- Visual Studio 15 2017
4854
- Visual Studio 15 2017 Win64
4955
- Visual Studio 15 2017 ARM
@@ -55,7 +61,9 @@ A `configuration` has these properties:
5561

5662
Because Ninja is designed for fast build speeds instead of flexibility and function, it is set as the default. However, some CMake projects may be unable to correctly build using Ninja. If this occurs, you can instruct CMake to generate a Visual Studio project instead.
5763

58-
To specify a Visual Studio generator, open the `CMakeSettings.json` from the main menu by choosing **CMake | Change CMake Settings**. Delete “Ninja” and type “V”. This activates IntelliSense, which enables you to choose the generator you want.
64+
To specify a Visual Studio generator in Visual Studio 2017, open the `CMakeSettings.json` from the main menu by choosing **CMake | Change CMake Settings**. Delete “Ninja” and type “V”. This activates IntelliSense, which enables you to choose the generator you want.
65+
66+
To specify a Visual Studio generator in Visual Studio 2019, right-click on the CMakeLists.txt file in **Solution Explorer** and choose **CMake Settings for project** > **Show Advanced Settings** > **Cmake Generator**.
5967

6068
When the active configuration specifies a Visual Studio generator, by default MSBuild.exe is invoked with `-m -v:minimal` arguments. To customize the build, inside the `CMakeSettings.json` file, you can specify additional [MSBuild command line arguments](../build/reference/msbuild-visual-cpp-overview.md) to be passed to the build system via the `buildCommandArgs` property:
6169

‎docs/build/configuring-programs-for-windows-xp.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,14 @@
11
---
22
title: "Configuring Programs for Windows XP"
3-
ms.date: "02/02/2018"
3+
ms.date: "05/16/2019"
44
ms.assetid: 1e4487b3-d815-4123-878b-5718b22f0fd5
55
---
66
# Configuring Programs for Windows XP
77

88
Because Visual Studio supports multiple platform toolsets, you can target operating systems and runtime libraries that are not supported by the default toolset. For example, by switching the platform toolset, you can use the C++11, C++14, and C++17 language enhancements supported by the MSVC compiler in Visual Studio to create apps that target Windows XP and Windows Server 2003. You can also use older platform toolsets to maintain binary-compatible legacy code and still take advantage of the latest features of the Visual Studio IDE.
99

10+
Visual Studio 2019 and later does not include support for creating code for Windows XP by using the v142 toolset. Support for Windows XP development by using the v141 toolset that shipped in Visual Studio 2017 is available as an optional component in the Visual Studio Installer.
11+
1012
## Install the Windows XP platform toolset
1113

1214
To get the platform toolset and components to target Windows XP and Windows Server 2003 in Visual Studio 2017, run the Visual Studio Installer. When you initially install Visual Studio or when you choose **Modify** to modify an existing installation, make sure that the **Desktop development with C++** workload is selected. In the list of optional components for this workload, choose **Windows XP support for C++**, and then choose **Install** or **Modify**.

‎docs/build/cppproperties-schema-reference.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "CppProperties.json schema reference"
3-
ms.date: "03/21/2019"
3+
ms.date: "05/16/2019"
44
helpviewer_keywords: ["CMake in Visual Studio"]
55
---
66

@@ -258,7 +258,7 @@ You have access to the following built-in macros inside `CppProperties.json`:
258258
|-|-|
259259
|`${workspaceRoot}`| the full path to the workspace folder|
260260
|`${projectRoot}`| the full path to the folder where `CppProperties.json` is placed|
261-
|`${vsInstallDir}`| the full path to the folder where the running instance of VS 2017 is installed|
261+
|`${vsInstallDir}`| the full path to the folder where the running instance of Visual Studio is installed|
262262

263263
For example, if your project has an include folder and also includes windows.h and other common headers from the Windows SDK, you may want to update your `CppProperties.json` configuration file with these includes:
264264

@@ -283,7 +283,7 @@ For example, if your project has an include folder and also includes windows.h a
283283
```
284284

285285
> [!Note]
286-
> `%WindowsSdkDir%` and `%VCToolsInstallDir%` are not set as global environment variables so make sure you start devenv.exe from a "Developer Command Prompt for VS 2017" that defines these variables.
286+
> `%WindowsSdkDir%` and `%VCToolsInstallDir%` are not set as global environment variables so make sure you start devenv.exe from a Developer Command Prompt that defines these variables. (Type "developer" in the Windows Start Menu.)
287287
288288
## Troubleshoot IntelliSense errors
289289

‎docs/build/customize-cmake-settings.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Customize CMake build settings in Visual Studio"
3-
ms.date: "04/25/2019"
3+
ms.date: "05/16/2019"
44
helpviewer_keywords: ["CMake build settings"]
55
---
66
# Customize CMake build settings

‎docs/build/how-to-enable-a-64-bit-visual-cpp-toolset-on-the-command-line.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "How to: Enable a 64-Bit MSVC Toolset on the Command Line"
3-
ms.date: "03/29/2018"
3+
ms.date: "05/16/2019"
44
helpviewer_keywords: ["x64 [C++]", "64-bit compiler [C++], command line usage", "64-bit compiler [C++], toolset enabling at command line", "command line [C++], 64-bit compiler", "Itanium [C++], command-line compiler", "IPF", "Itanium [C++]", "IPF, command-line compiler", "x64 [C++], command-line compiler"]
55
ms.assetid: 4da93a19-e20d-4778-902a-5eee9a6a90b5
66
---
@@ -17,7 +17,7 @@ When you install a C++ workload in the Visual Studio installer, it always instal
1717

1818
## Use a 64-bit hosted developer command prompt shortcut
1919

20-
When Visual Studio is installed on a 64-bit Windows operating system, additional developer command prompt shortcuts for the 64-bit, x64-hosted native and cross compilers are available. To access these command prompts on Windows 10, on the **Start** menu, open the folder for your version of Visual Studio, for example **Visual Studio 2017**, and then choose one of the x64 native or cross-tool developer command prompts. To access these command prompts on Windows 8, on the **Start** screen, open **All apps**. Under the heading for the installed version of Visual Studio, open the **Visual Studio** folder (in older versions of Visual Studio, it may be named **Visual Studio Tools**). On earlier versions of Windows, choose **Start**, expand **All Programs**, the folder for your version of **Visual Studio** (and on older versions of Visual Studio, **Visual Studio Tools**). For more information, see [Developer command prompt shortcuts](building-on-the-command-line.md#developer_command_prompt_shortcuts).
20+
When Visual Studio is installed on a 64-bit Windows operating system, additional developer command prompt shortcuts for the 64-bit, x64-hosted native and cross compilers are available. To access these command prompts on Windows 10, on the **Start** menu, open the folder for your version of Visual Studio, for example **Visual Studio 2019**, and then choose one of the x64 native or cross-tool developer command prompts. To access these command prompts on Windows 8, on the **Start** screen, open **All apps**. Under the heading for the installed version of Visual Studio, open the **Visual Studio** folder (in older versions of Visual Studio, it may be named **Visual Studio Tools**). On earlier versions of Windows, choose **Start**, expand **All Programs**, the folder for your version of **Visual Studio** (and on older versions of Visual Studio, **Visual Studio Tools**). For more information, see [Developer command prompt shortcuts](building-on-the-command-line.md#developer_command_prompt_shortcuts).
2121

2222
## Use Vcvarsall.bat to set a 64-bit hosted build architecture
2323

‎docs/build/how-to-integrate-custom-tools-into-the-project-properties.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "How to: Integrate Custom Tools into the Project Properties"
3-
ms.date: "04/27/2016"
3+
ms.date: "05/16/2019"
44
helpviewer_keywords: ["msbuild (c++), howto: integrate custom tools"]
55
ms.assetid: f32d91a4-44e9-4de3-aa9a-1c7f709ad2ee
66
---
@@ -16,15 +16,15 @@ This document explains how to create a file in a set directory that contains pro
1616

1717
1. In the XML editor, create an XML file.
1818

19-
1. Save the file in the Visual Studio 2017 `VCTargets\1033` folder. You will have a different path for each edition of Visual Studio 2017 that is installed and each language. For example, the folder path for Visual Studio Enterprise edition in English is `%ProgramFiles%\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\1033`. Adjust the path for your language and Visual Studio edition. Every rule in the **Property Pages** window is represented by an XML file in this folder. Make sure that the file is uniquely named in the folder.
19+
1. Save the file in the Visual Studio `VCTargets\1033` folder. You will have a different path for each edition of Visual Studio that is installed and each language. For example, the default folder path for Visual Studio 2019 Community edition in English is `C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\VC\VCTargets`. Adjust the path for your language and Visual Studio edition. Every rule in the **Property Pages** window is represented by an XML file in this folder. Make sure that the file is uniquely named in the folder.
2020

21-
1. Copy the content of `%ProgramFiles%\Microsoft Visual Studio\2017\<VS Edition>\Common7\IDE\VC\VCTargets\<LCID>\cl.xml`, close it without saving changes, and then paste the content in your new XML file. You can use any XML schema file - this is just one that can be used so you start with a template.
21+
1. Copy the content of `%ProgramFiles%\Microsoft Visual Studio\2019\<VS Edition>\Common7\IDE\VC\VCTargets\<LCID>\cl.xml` (or whatever your path is), close it without saving changes, and then paste the content in your new XML file. You can use any XML schema file - this is just one that can be used so you start with a template.
2222

2323
1. In the new XML file, modify the content according to your requirements. Make sure to change the **Rule Name** and **Rule.DisplayName** at the top of the file.
2424

2525
1. Save the changes and close the file.
2626

27-
1. The XML files in `%ProgramFiles%\Microsoft Visual Studio\2017\<VS Edition>\Common7\IDE\VC\VCTargets\<LCID>` are loaded when Visual Studio starts. Therefore, to test the new file, restart Visual Studio.
27+
1. The XML files in `%ProgramFiles%\Microsoft Visual Studio\2019\<VS Edition>\Common7\IDE\VC\VCTargets\<LCID>` (or wherever you saved them) are loaded when Visual Studio starts. Therefore, to test the new file, restart Visual Studio.
2828

2929
1. In **Solution Explorer**, right-click a project and then click **Properties**. In the **Property Pages** window, in the left pane, verify that there is a new node with the name of your Rule.
3030

‎docs/build/project-property-inheritance.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Property inheritance in Visual Studio projects - C++"
3-
ms.date: "12/10/2018"
3+
ms.date: "05/16/2019"
44
helpviewer_keywords: ["C++ projects, property inheritance"]
55
---
66

@@ -10,7 +10,7 @@ The Visual Studio project system is based on MSBuild, which defines file formats
1010

1111
## The .vcxproj file, .props files and .targets files
1212

13-
Project properties are stored either directly in the project file (*.vcxproj) or in other .targets or .props files that the project file imports and which supply default values. For Visual Studio 2015, these files are located in **\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140**. For Visual Studio 2017, these files are located in **\\Program Files (x86)\\Microsoft Visual Studio\\2017\\_edition_\\Common7\\IDE\\VC\\VCTargets**, where _edition_ is the Visual Studio edition installed. Properties are also stored in any custom .props files that you might add to your own project. We highly recommend that you NOT edit those files manually, and instead use the property pages in the IDE to modify all properties, especially those that participate in inheritance, unless you have a very good understanding of MSBuild.
13+
Project properties are stored either directly in the project file (*.vcxproj) or in other .targets or .props files that the project file imports and which supply default values. For Visual Studio 2015, these files are located in **\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140**. For Visual Studio 2017 or Visual Studio 2019, these files are located in **\\Program Files (x86)\\Microsoft Visual Studio\\&lt;2017 or 2019>\\_edition_\\Common7\\IDE\\VC\\VCTargets**, where _edition_ is the Visual Studio edition installed. Properties are also stored in any custom .props files that you might add to your own project. We highly recommend that you NOT edit those files manually, and instead use the property pages in the IDE to modify all properties, especially those that participate in inheritance, unless you have a very good understanding of MSBuild.
1414

1515
As shown earlier, the same property for the same configuration may be assigned a different value in these different files. When you build a project, the MSBuild engine evaluates the project file and all the imported files in a well-defined order (described below). As each file is evaluated, any property values defined in that file will override the existing values. Any values that are not specified are inherited from files that were evaluated earlier. Therefore, when you set a property with property pages, it is also important to pay attention to where you set it. If you set a property to "X" in a .props file, but the property is set to "Y" in the project file, then the project will build with the property set to "Y". If the same property is set to "Z" on a project item, such as a .cpp file, then the MSBuild engine will use the "Z" value.
1616

‎docs/build/reference/clr-common-language-runtime-compilation.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "/clr (Common Language Runtime Compilation)"
3-
ms.date: "09/18/2018"
3+
ms.date: "05/16/2019"
44
f1_keywords: ["/CLR", "VC.Project.VCNMakeTool.CompileAsManaged", "VC.Project.VCCLCompilerTool.CompileAsManaged"]
55
helpviewer_keywords: ["cl.exe compiler, common language runtime option", "-clr compiler option [C++]", "clr compiler option [C++]", "/clr compiler option [C++]", "Managed Extensions for C++, compiling", "common language runtime, /clr compiler option"]
66
ms.assetid: fec5a8c0-40ec-484c-a213-8dec918c1d6c
@@ -24,11 +24,11 @@ One or more of the following switches, comma-separated.
2424

2525
- **pure**
2626

27-
**/clr:pure is deprecated**. The option is removed in Visual Studio 2017. We recommend that you port code that must be pure MSIL to C#.
27+
**/clr:pure is deprecated**. The option is removed in Visual Studio 2017 and later. We recommend that you port code that must be pure MSIL to C#.
2828

2929
- **safe**
3030

31-
**/clr:safe is deprecated**. The option is removed in Visual Studio 2017. We recommend that you port code that must be safe MSIL to C#.
31+
**/clr:safe is deprecated**. The option is removed in Visual Studio 2017 and later. We recommend that you port code that must be safe MSIL to C#.
3232

3333
- **noAssembly**
3434

‎docs/build/reference/clr-restrictions.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ Note the following restrictions on the use of **/clr**:
6363

6464
- Functions that take a variable number of arguments (varargs) will be generated as native functions. Any managed data types in the variable argument position will be marshaled to native types. Note that <xref:System.String?displayProperty=fullName> types are actually wide-character strings, but they are marshaled to single-byte character strings. So if a printf specifier is %S (wchar_t*), it will marshal to a %s string instead.
6565

66-
- When using the va_arg macro, you may get unexpected results when compiling with **/clr:pure**. For more information, see [va_arg, va_copy, va_end, va_start](../../c-runtime-library/reference/va-arg-va-copy-va-end-va-start.md). The **/clr:pure** and **/clr:safe** compiler options are deprecated in Visual Studio 2015 and unsupported in Visual Studio 2017. Code that must be "pure" or "safe" should be ported to C#.
66+
- When using the va_arg macro, you may get unexpected results when compiling with **/clr:pure**. For more information, see [va_arg, va_copy, va_end, va_start](../../c-runtime-library/reference/va-arg-va-copy-va-end-va-start.md). The **/clr:pure** and **/clr:safe** compiler options are deprecated in Visual Studio 2015 and unsupported in Visual Studio 2017 and later. Code that must be "pure" or "safe" should be ported to C#.
6767

6868
- You should not call, from managed code, any functions that walk the stack to get parameter information (function arguments); the P/Invoke layer causes that information to be further down the stack. For example, do not compile proxy/stub with **/clr**.
6969

0 commit comments

Comments
 (0)