Skip to content

Commit f223475

Browse files
author
mikeblome
committed
new image and tweaked text
1 parent 75bfe23 commit f223475

File tree

3 files changed

+4
-3
lines changed

3 files changed

+4
-3
lines changed
19.5 KB
Loading

docs/ide/property-page-xml-files.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,9 @@ The only scenarios in which you need to understand the internal workings of thes
4040

4141
First, let's open the property pages for a project (right click on the project node in **Solution Explorer** and choose Properties):
4242

43+
![Visual C++ Project Properties](media/cpp-property-page-2017.png)
4344

44-
Each node under **Configuration Properties** is called a Rule. A Rule sometimes represents a single tool like the compiler, but in general the term refers to something that has properties, that executes and that may produce some output. Each rule is populated from an xml file in the VCTargets folder. For example, the C/C++ rule that is above is populated by `cl.xml'.
45+
Each node under **Configuration Properties** is called a Rule. A Rule sometimes represents a single tool like the compiler, but in general the term refers to something that has properties, that executes and that may produce some output. Each rule is populated from an xml file in the VCTargets folder. For example, the C/C++ rule that is shown above is populated by `cl.xml'.
4546

4647
As shown above, each Rule has a set of properties which are organized into categories. Each sub-node under a Rule represents a category. For example, the Optimization node under C/C++ contains all the optimization-related properties of the compiler tool. The properties and their values themselves are rendered in a grid format on the right pane.
4748

docs/ide/vcxproj-file-structure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ translation.priority.ht:
3434
---
3535

3636
# .vcxproj and .props file structure
37-
MSBuild is the default project system in Visual Studio; when you choose **File | New Project** in Visual C++ you are creating an MSBuild project whose settings are stored in an XML project file that has the extension `.vcxproj`. The project file may also import .props files and .targets files where settings can be stored. In most cases, you never need to manually edit the project file, and in fact you should not edit it manually unless you have a good understanding of MSBuild. Whenever possible you should use the Visual Studio property pages to modify project settings. However, in some cases you may need to modify a project file or property sheet manually. For those scenarios, this article contains basic information about the structure of the file.
37+
MSBuild is the default project system in Visual Studio; when you choose **File | New Project** in Visual C++ you are creating an MSBuild project whose settings are stored in an XML project file that has the extension `.vcxproj`. The project file may also import .props files and .targets files where settings can be stored. In most cases, you never need to manually edit the project file, and in fact you should not edit it manually unless you have a good understanding of MSBuild. Whenever possible you should use the Visual Studio property pages to modify project settings (see [Working with project properties](working-with-project-properties.md). However, in some cases you may need to modify a project file or property sheet manually. For those scenarios, this article contains basic information about the structure of the file.
3838

3939
**Important:**
4040
If you choose to manually edit a .vcxproj file, be aware of these facts:
@@ -166,7 +166,7 @@ This group contains imports for the Build Customization target files.
166166

167167
## How the IDE uses element labels
168168

169-
In the IDE, when you set the UseOfAtl property in the general property page, it is written to the Configuration property group in the project file, while the TargetName property in the same property page is written to the label-less property group. Visual Studio looks at the property page's xml file for the information on where to write each property. For the General property page, that file is `%ProgramFiles(x86)%\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\1033\general.xml`. The property page XML file defines the static information about a Rule and all its properties. One such piece of information is the preferred position of a Rule property in the destination file (the file where its value will be written). The preferred position is specified by the Label attribute on the project file elements.
169+
In the IDE, when you set the UseOfAtl property in the general property page, it is written to the Configuration property group in the project file, while the TargetName property in the same property page is written to the label-less property group. Visual Studio looks at the property page's xml file for the information on where to write each property. For the General property page (assuming you have an English version of Visual Studio Enterprise Edition), that file is `%ProgramFiles(x86)%\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\1033\general.xml`. The property page XML file defines the static information about a Rule and all its properties. One such piece of information is the preferred position of a Rule property in the destination file (the file where its value will be written). The preferred position is specified by the Label attribute on the project file elements.
170170

171171

172172
## Property Sheet layout

0 commit comments

Comments
 (0)