Skip to content

Commit f238043

Browse files
committed
Clarify recommendations for use of rule set files
1 parent b7582cc commit f238043

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/code-quality/analyzers-faq.yml

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
### YamlMime:FAQ
22
metadata:
33
title: EditorConfig versus analyzers
4-
ms.date: 10/05/2021
4+
ms.date: 08/15/2025
55
description: Learn about .NET Compiler Platform-based code analysis in Visual Studio. See answers to questions about EditorConfig files, rule sets, and other topics.
66
ms.topic: faq
77
helpviewer_keywords:
@@ -30,7 +30,9 @@ sections:
3030
answer: |
3131
Rule sets and EditorConfig files can coexist and can both be used to configure analyzers. Both EditorConfig files and rule sets let you enable and disable rules and set their severity.
3232
33-
However, EditorConfig files offer additional ways to configure rules too:
33+
However, in Visual Studio 2019 version 16.5 and later, rule set files are deprecated in favor of EditorConfig files, and .NET Core and .NET 5+ projects don't support all the rule set menu commands. For more information, see [Convert an existing rule set file to an EditorConfig file](../code-quality/use-roslyn-analyzers.md#convert-an-existing-rule-set-file-to-an-editorconfig-file).
34+
35+
EditorConfig files offer additional ways to configure rules:
3436
3537
- For the .NET code-quality analyzers, EditorConfig files let you [define which types of code to analyze](/dotnet/fundamentals/code-analysis/code-quality-rule-options).
3638
- For the .NET code-style analyzers that are built into Visual Studio, EditorConfig files let you [define the preferred code styles](/dotnet/fundamentals/code-analysis/code-style-rule-options) for a codebase.

0 commit comments

Comments
 (0)