You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build/reference/vcxproj-file-structure.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,9 +21,9 @@ For manual editing scenarios, this article contains basic information about the
21
21
22
22
If you choose to manually edit a *`.vcxproj`* file, be aware of these facts:
23
23
24
-
1. The structure of the file must follow a prescribed form, which is described in this article.
24
+
- The structure of the file must follow a prescribed form, which is described in this article.
25
25
26
-
1. The Visual Studio C++ project system currently doesn't support wildcards or lists directly in project items. For example, these forms aren't supported:
26
+
- The Visual Studio C++ project system currently doesn't support wildcards or lists directly in project items. For example, these forms aren't supported:
27
27
28
28
```xml
29
29
<ItemGroup>
@@ -34,7 +34,7 @@ If you choose to manually edit a *`.vcxproj`* file, be aware of these facts:
34
34
35
35
For more information on wildcard support in projects and possible workarounds, see [`.vcxproj` files and wildcards](vcxproj-files-and-wildcards.md).
36
36
37
-
1. The Visual Studio C++ project system currently doesn't support macros in project item paths. For example, this form isn't supported:
37
+
- The Visual Studio C++ project system currently doesn't support macros in project item paths. For example, this form isn't supported:
38
38
39
39
```xml
40
40
<ItemGroup>
@@ -44,13 +44,13 @@ If you choose to manually edit a *`.vcxproj`* file, be aware of these facts:
44
44
45
45
"Not supported" means that macros aren't guaranteed to work for all operations in the IDE. Macros that don't change their value in different configurations should work, but might not be preserved if an item is moved to a different filter or project. Macros that change their value for different configurations will cause problems. That's because the IDE doesn't expect project item paths to be different for different project configurations.
46
46
47
-
1. To add, remove, or modify project properties correctly when you edit them in the **Project Properties** dialog, the file must contain separate groups for each project configuration. The conditions must be in this form:
47
+
- To add, remove, or modify project properties correctly when you edit them in the **Project Properties** dialog, the file must contain separate groups for each project configuration. The conditions must be in this form:
1. Each property must be specified in the group with correct label, as specified in the property rule file. For more information, see [Property page xml rule files](property-page-xml-files.md).
53
+
- Each property must be specified in the group with its correct label, as specified in the property rule file. For more information, see [Property page xml rule files](property-page-xml-files.md).
0 commit comments