Configuring FxCop

It is possible to incorporate FxCop results in the TICS output for C# files. FxCop is a static analyzer from Microsoft. It checks a set of rules on .NET assemblies.

Important Note: TICS only shows those FxCop violations that can be related back to the file that is being analyzed. FxCop also checks application wide rules but without referencing an offending source file. These violations are ignored by TICS.

Prerequisites

For a successful FxCop integration, the following prerequisites must be met.

• FxCop 1.36 must be installed/accessible on the TICS file server in chk\FxCop.
• If the TICS file server is on a network share, FxCop must be granted permissions to be run from the share (it is a .NET application).
• The file to be analyzed must occur in a Visual Studio 8 or 9 (2005, 2008) .csproj project file.
• The project -- and, therefore, the resulting assembly -- must have been successfully built.

Basic configuration

The FxCop analyzer requires the BUILDTYPE to be properly set.

BUILDTYPE: [ { 'name': 'CSProj', 'compiler': ['None'] } ]

A standard FxCop rule configuration is available in the form of a IMPL.txt, RULES.txt pair.

Warning reference

See FxCop Warnings for a list of all FxCop warnings.