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
{{ message }}
Repository navigation
Commit f9344b0
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/code-quality/using-rule-sets-to-specify-the-cpp-rules-to-run.md
+142Lines changed: 142 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -102,3 +102,145 @@ The following example shows a basic rule set file that you can use as a starting
102
102
```
103
103
104
104
::: moniker-end
105
+
106
+
## Ruleset schema
107
+
108
+
The following ruleset schema describes the XML schema of a ruleset file. The ruleset schema is stored in `%VSINSTALLDIR%\Team Tools\Static Analysis Tools\Schemas\RuleSet.xsd`. You can use it to author your own rulesets programmatically or to validate whether your custom rulesets adhere to the correct format. For more information, see [How to: Create an XML document based on an XSD schema](https://docs.microsoft.com/visualstudio/xml-tools/how-to-create-an-xml-document-based-on-an-xsd-schema?view=vs-2019).
- TLocalization: Localization information including name of the ruleset file, description of the ruleset file, name of the resource assembly containing the localized resource, and base name of the localized resource.
234
+
- TRuleHintPaths: File paths used as hints to search for ruleset files.
235
+
- TName: Name of the current ruleset file.
236
+
- TDescription: Description of the current ruleset file.
237
+
- TInclude: Path to an included ruleset with rule action.
238
+
- TIncludeAll: Rule action for all rules.
239
+
- TRule: Rule ID with rule action.
240
+
- TRules: Collection of one or more rules.
241
+
- TRuleSet: Ruleset file format consisting of localization information, rule hint paths, include all information, include information, rules information, name, description, and tools version information.
242
+
- TRuleAction: Enumeration describing a rule action such as an error, warning, info, hidden, or none.
243
+
- TIncludeAction: Enumeration describing a rule action such as an error, warning, info, hidden, none, or default.
244
+
- TIncludeAllAction: Enumeration describing a rule action such as an error, warning, info, or hidden.
245
+
246
+
To see an example of a ruleset, see [To create a rule set in a text editor](#to-create-a-rule-set-in-a-text-editor), or any of the default rulesets stored in `%VSINSTALLDIR%\Team Tools\Static Analysis Tools\Rule Sets`.
Copy file name to clipboardExpand all lines: docs/linux/cmake-linux-project.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "Create and configure a Linux CMake project in Visual Studio"
3
3
description: "How to create, configure, edit, and compile a Linux CMake project in Visual Studio"
4
-
ms.date: "05/03/2020"
4
+
ms.date: "06/22/2020"
5
5
ms.assetid: f8707b32-f90d-494d-ae0b-1d44425fdc25
6
6
---
7
7
# Create and configure a Linux CMake project
@@ -114,8 +114,14 @@ After you select a target, CMake runs automatically on the Linux system to gener
114
114
115
115

116
116
117
+
### Intellisense
118
+
117
119
To provide IntelliSense support for headers on remote Linux systems, Visual Studio automatically copies them from the Linux machine to a directory on your local Windows machine. For more information, see [IntelliSense for remote headers](configure-a-linux-project.md#remote_intellisense).
118
120
121
+
### Locale
122
+
123
+
For more information, see [Linux target locale](configure-a-linux-project.md#locale).
124
+
119
125
## <aname="debug_cmake_project"></a> Debug the CMake project
120
126
121
127
To debug your code on the specified target system, set a breakpoint. Select the CMake target as the startup item in the toolbar menu next to the project setting. Then choose **⏵ Start** on the toolbar, or press **F5**.
Copy file name to clipboardExpand all lines: docs/linux/configure-a-linux-project.md
+10-6Lines changed: 10 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: "Configure a C++ Linux project in Visual Studio"
3
-
ms.date: "06/11/2019"
3
+
ms.date: "06/22/2020"
4
4
ms.assetid: 4d7c6adf-54b9-4b23-bd23-5de0c825b768
5
5
---
6
6
# Configure a Linux project
@@ -27,7 +27,7 @@ You can configure a Linux project to target a physical Linux machine, a virtual
27
27
28
28
## General settings
29
29
30
-
To view configuration options, select the **Project > Properties** menu, or rightclick on the project in **Solution Explorer** and select **Properties** from the context menu. The **General** settings appear.
30
+
To view configuration options, select the **Project > Properties** menu, or right-click on the project in **Solution Explorer** and select **Properties** from the context menu. The **General** settings appear.
@@ -37,7 +37,7 @@ For more information about the settings in the property pages, see [Linux Projec
37
37
38
38
## Remote settings
39
39
40
-
To change settings pertaining to the remote Linux computer, configure the remote settings that appear under [General](prop-pages/general-linux.md).
40
+
To change settings related to the remote Linux computer, configure the remote settings that appear under [General](prop-pages/general-linux.md).
41
41
42
42
- To specify a remote target Linux computer, use the **Remote Build Machine** entry. This will allow you to select one of the connections created previously. To create a new entry, see the [Connecting to Your Remote Linux Computer](connect-to-your-remote-linux-computer.md) section.
43
43
@@ -66,17 +66,17 @@ To change settings pertaining to the remote Linux computer, configure the remote
66
66
67
67
::: moniker range="vs-2019"
68
68
69
-
This section does not apply when targeting WSL.
69
+
This section doesn't apply when targeting WSL.
70
70
71
71
::: moniker-end
72
72
73
73
When building on remote systems, the source files on your development PC are copied to the Linux computer and compiled there. By default, all sources in the Visual Studio project are copied to the locations set in the settings above. However, additional sources can also be added to the list, or copying sources can be turned off entirely, which is the default for a Makefile project.
74
74
75
-
-**Sources to copy** determines which sources are copied to the remote computer. By default, the **\@(SourcesToCopyRemotely)** defaults to all source code files in the project, but does not include any asset/resource files, such as images.
75
+
-**Sources to copy** determines which sources are copied to the remote computer. By default, the **\@(SourcesToCopyRemotely)** defaults to all source code files in the project, but doesn't include any asset/resource files, such as images.
76
76
77
77
-**Copy sources** can be turned on and off to enable and disable the copying of source files to the remote computer.
78
78
79
-
-**Additional sources to copy** allows you to add additional source files which will be copied to the remote system. You can specify a semi-colon delimited list, or you can use the **:=** syntax to specify a local and remote name to use:
79
+
-**Additional sources to copy** allows you to add additional source files, which will be copied to the remote system. You can specify a semi-colon delimited list, or you can use the **:=** syntax to specify a local and remote name to use:
@@ -117,6 +117,10 @@ You can enable logging to help troubleshoot problems:
117
117
118
118
::: moniker-end
119
119
120
+
## <aname="locale"></a> Linux target locale
121
+
122
+
Visual Studio language settings aren't propagated to Linux targets because Visual Studio doesn't manage or configure installed packages. Messages shown in the **Output** window, such as build errors, are shown using the language and locale of the Linux target. You'll need to configure your Linux targets for the desired locale.
123
+
120
124
## See also
121
125
122
126
[Set compiler and build properties](../build/working-with-project-properties.md)<br/>
0 commit comments