Plugin Information
View FxCop Runner on the plugin site for more information.

FxCopCmd.exe execute plugin.

Description

FxCopCmd.exe execute plugin.
Output xml can be used to Violations Plugin.

Configuration

System configuration

Open the system configuration page "Manage Jenkins->Configure system"
Enter the path to the FxCop command line client, that should be used by Jenkins.

Example: C:\Program Files (x86)\Microsoft Fxcop 10.0\FxCopCmd.exe

Job configuration

name	description
FxCop Name	Select FxCop.
Assembly Files	Assembly file(s) to analyze. You can specify multiple analyze assemblies by separating them with new-line or space.
Output XML	FxCop project or XML report output file.
RuleSet File	Rule set to be used for the analysis.
IgnoreGeneratedCode	Suppress analysis results against generated code.
ForceOutput	Write output XML and project files even in the case where no violations occurred.
Command Line Arguments	This is a whitespace separated list of command line arguments you can specify.
Fail build on test failure	Fail build on test failure

Common Problems

FxCopCmd.exe can produce several warnings, and when it does, the build will be marked as unstable. Look in your console output for the fxcop output.

Console output contains

Resolution

There were non-critical errors loading FxCop project:

* Could not import all messages.
* End of project load errors.

This can happen if you are using an FxCop project file with some of the default settings.

Open your project in FxCop
Choose Project -> Project Options
Under Save Messages and next to Project uncheck the Active checkbox
click OK

See also: "Could not import all messages." error supression

NOTE: One or more referenced assemblies could not be found.
Use the '/directory' or '/reference' switch to specify additional assembly
reference search paths.

FxCop can't find the assemblies you reference. Two possible solutions:

add the /gac flag to FxCop
change the FxCopCmd.exe.config file to use a more forgiving assembly matching strategy
- Open FxCopCmd.exe.config and change AssemblyReferenceResolveMode from StrongName to StrongNameIgnoringVersion
- the location of FxCopCmd.exe.config depends on your installation, and may require administrator permission to edit
  
  See also: changing FxCopCmd.exe.config

Jenkins : FxCop Runner Plugin

Description

Configuration

System configuration

Job configuration

Common Problems

Changelog

Version 1.1 (02/28/2013)

Version 1.0 (02/26/2013)

Attachments: