This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "FxCop" – news ·newspapers ·books ·scholar ·JSTOR(May 2013) (Learn how and when to remove this message) |
| FxCop | |
|---|---|
| Developer | Microsoft |
| Stable release | 10.0 / 2010; 16 years ago (2010) |
| Operating system | Microsoft Windows |
| Type | Static code analysis tool |
| Website | msdn |
FxCop is a freestatic code analysis tool fromMicrosoft that checks.NETmanaged codeassemblies for conformance to Microsoft's .NET Framework Design Guidelines.
UnlikeStyleCop, or theLint programming tool, for theC programming language, FxCop analyzes the compiledobject code, not the originalsource code. It usesCIL parsing andcallgraph analysis to inspect assemblies for more than 200 different possible coding standards violations in the following areas:
FxCop includes bothGUI and command line versions of the tool. MicrosoftVisual Studio 2005 andVisual Studio 2008Team System Development Editions both include a "Code Analysis" feature based on FxCop. For Visual Studio 2010 the corresponding, and slightly enhanced, static code analysis features are included in the Premium and Ultimate editions. FxCop 10.0 is included in theMicrosoft Windows SDK forWindows 7.[1]
FxCop provides a tool to help developers to follow their company's coding standards. FxCop does code analysis to check whether the new code is compliant with the coding standards and naming conventions followed by the company. FxCop will ensure that the specified rules are used in the source code.[citation needed]