16 packages tagged with “FxCop”
Tool for static analysis of Visual Studio solutions and projects.
Automatically Installs FxCop build targets and settings into a project so you have reasonable defaults. Requires Visual Studio with Code Analysis or FxCop 10 (available from your Windows SDK).
Gendarme is a extensible rule-based tool to find problems in .NET applications and libraries. Gendarme inspects programs and libraries that contain code in ECMA CIL format (Mono and .NET) and looks for common problems with the code, problems that compiler do not typically check or have not historically checked.
Tool - Parse analysis reports (InspectCode, ...) and send messages to build server or console.
Utility to convert ruleset files to equivalent .editorconfig files. Editorconfig files are respected by C# and VB compilers on VS2019 16.3 or later. See https://learn.microsoft.com/visualstudio/code-quality/use-roslyn-analyzers#set-rule-severity-in-an-editorconfig-file for details.
Overrides for FxCop style rules.
Parse analysis reports (InspectCode, ...) and send messages to build server or console.
This package provides additional rules specifically implemented for Script# code and scripting scenarios.
FxCop rule additions.
Command-line tool for detecting available updates of NuGet packages.
General purpose Roslyn-based static code analysis rules for C#. While not intended to be an exact replacement for StyleCop, many of the individual diagnostics are similar to StyleCop rules.
Reports diagnostics, helping you to annotate your source tree with (Item)NotNull / (Item)CanBeNull attributes. See also: https://www.jetbrains.com/resharper/help/Code_Analysis__Code_Annotations.html You need Visual Studio 2013/2012/2010 and Resharper v8 or higher to use this analyzer. See package "ResharperCodeContractNullability" if you use Visual Studio 2015.
Visual Studio solution structure and settings validator.
.NET standard tooling build that leverages Roslyn analyzers, rulesets and additional configuration to be used for Code Analysis.