FxCop is an analysis tool for. NET. It checks the CIL code and the call multi- graph of the individual routines after infringements of design guidelines from Microsoft and on potential weak points.
The software is a console based principle. However, FxCop can be called as an external tool after the build process. There is also a plugin for Visual Studio 2008 and Visual Studio 2005. In Visual Studio Team System and SharpDevelop it is integrated. There also exists a GUI for the stand-alone operation.
FxCop analyzes primarily seven areas:
- Nomenclature ( dictionary and case-sensitive )
- Reusability of code and interoperability
- References to objects and unnecessary allocation
- Safety compliance violations
- General design guidelines for architecture
- Performance guidelines
- Globalization policies
FxCop analyzes the loaded assemblies. Here, the CIL code is verified and the call graph analysis. FxCop uses this policy, according to which the individual criteria are cross-checked. In the user configuration can be specified as a policy is handled. In addition, can be about preprocessor checking through the source code control. Thus, for example, complained, but required error, such as a deliberate and unavoidable design infringement are excluded from the examination without general to prevent the review of this policy.
FxCop is both command line based as controlled via a GUI. A Visual Studio integration is possible. FxCop can be well evaluated by the Team Foundation Server. It performs a check of the software can be prevented, for example, in breach of the guidelines. Policy violations can be evaluated by metrics, integrate by reports in TFS and thus flow in assessing the quality of a software with a.
FxCop needed for execution. NET 2.0, but it supports the review of all versions 1.1 to 3.5.