Microsoft fxcop

FxCopAnalyzers to the. NET analyzers:. Enable or install. NET analyzers. Note that you do not need to change your project's target platform. Enable additional rules: Microsoft. NetAnalyzers is much more conservative compared to Microsoft.

Unlike FxCopAnalyzers package, it only has a few correctness rules which are enabled by default as build warnings. For example, setting the property to AllEnabledByDefault will enable all the applicable CA rules as build warnings by default. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. NET analyzers. This page lists the rules that have been ported. See Unported rules for those that haven't been ported and whether there are plans to port them.

The autogenerated documentation page in the roslyn-analyzers repo has the most up-to-date list of rules that have been ported to Roslyn analyzers. That page also has additional information, such as whether the rule is enabled by default and if it has an associated code fix. Code fixes are one-click fixes available in the light bulb icon menu in Visual Studio. As of the date on this page, the list of FxCop rules that have been ported to.

For more information on the differences between legacy analysis and source analysis, see the following:. Source code analysis versus legacy analysis. FAQ about. NET analyzers. Enable or install the. Like legacy analysis rule violations, source code analysis violations appear in the Error List window in Visual Studio.

In addition, source code analysis violations also show up in the code editor as squiggles under the offending code. The color of the squiggle depends on the severity setting of the rule. To see the status of rules ported to the new. NET analyzers, see Ported and unported rules. Prior to Visual Studio NET 5. FxCopAnalyzers NuGet package. Starting in Visual Studio