FxCop
This page contains reference information about the .NET FxCop Build Runner fields.
You can also import an XML file, generated by your own build script, through Build Script Interaction with TeamCity.
Option | Description |
|---|---|
Build runner | Select FxCop from the drop-down list. |
FxCop Options
Option | Description |
|---|---|
What to inspect | Check one of the following options to specify object to inspect (either particular assemblies or a project) |
Assemblies | Enter paths, relative to the Build Checkout Directory and separated by spaces, to inspected assemblies (use ant-like wildcards to select files by mask). FxCop will use default settings to inspect them. Enter exclude wildcards to refine included assemblies list. |
Project | Enter the path (relative to the Build Checkout Directory) to previously prepared FxCop project from FxCop GUI |
Search referenced assemblies in GAC | Search assemblies, referenced by targets, in Global Assembly Cache |
Search referenced assemblies in directories | Search assemblies, referenced by targets, in specified directories separated by spaces |
Ignore generated code | New option introduced in FxCop 1.36. Speeds up inspection |
Report XSLT file | The path to XSLT transformation file, relative to the Build Checkout Directory or absolute on agent machine. You can use path to detected FxCop on target machine (i.e. "%system.FxCopRoot%/Xml/FxCopReport.xsl"). When Report XSLT file option is set, the build runner will apply XSLT transform to FxCop XML output and display resulting HTML to a new tab "FxCop" on the build results page. |
Additional FxCopCmd options | Additional options for calling FxCopCmd executable. All options entered in this field will be added to the beginning of command line parameters |
FxCop Location
Option | Description |
|---|---|
FxCop installation root | Mandatory parameter. Specify the path to the FxCop installation root on an agent machine, or a path to the FxCop executable relative to the Build Checkout Directory. Default value set to " |