Skip to content

Commit bf0db16

Browse files
authored
Configuration.md: Add link to rule set example file
1 parent 19aefb8 commit bf0db16

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

documentation/Configuration.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ StyleCop Analyzers is configured using two separate mechanisms: code analysis ru
1414

1515
Code analysis rule sets are the standard way to configure most diagnostic analyzers within Visual Studio. Information about creating and customizing these files can be found in the [Using Rule Sets to Group Code Analysis Rules](https://docs.microsoft.com/visualstudio/code-quality/using-rule-sets-to-group-code-analysis-rules) documentation on docs.microsoft.com.
1616

17+
Here is an example `.ruleset` file from the Roslyn SDK: https://github.com/dotnet/roslyn-sdk/blob/3e94c5fe1ee981a885c34e2e39383bc4420f2557/RoslynSDK.ruleset. This file illustrates how the severities for individual rules can easily be configured as needed.
18+
1719
## Getting Started with **stylecop.json**
1820

1921
The easiest way to add a **stylecop.json** configuration file to a new project is using a code fix provided by the project. To invoke the code fix, open any file where SA1633 is reported¹ and press Ctrl+. to bring up the Quick Fix menu. From the menu, select **Add StyleCop settings file to the project**.

0 commit comments

Comments
 (0)