TeamCity
 
You are viewing the documentation for an earlier version of TeamCity.

FxCop

Last modified: 20 April 2023

The Build Runner is intended for inspecting .NET assemblies and reporting possible design, localization, performance, and security improvements. If you want TeamCity to display FxCop reports, you can either configure the corresponding build runner, or import XML reports by means of service messages if you prefer to run the FxCop tool directly from the script.

For the list of supported FxCop versions, see Supported Platforms and Environments.

FxCop Build Runner Settings



FxCop Installation



What to inspect



FxCop Options



Build failure conditions



Check the box to fail a build on the specified analysis errors. Click Build Failure Conditions to define the number of the errors.

Using Service Messages



If you prefer to call the FxCop tool directly from the script, not as a build runner, you can use the importData Build Script Interaction with TeamCity to import an xml file generated by the FxCopCmd tool into TeamCity. In this case the FxCop tool results will appear in the Working with Build Results of the build results page.

The Build Script Interaction with TeamCity format is described below:

##teamcity[importData type='FxCop' path='<path to the xml file>']