I integrated FxCop with CruiseControl.NET and NAnt for a .NET 2.0 project today. A couple of notes that might be useful for anyone doing the same.
I copied the fxcop directory from the VS.NET folder (inside of Team Tools, I think) into my tools directory, so it will be checked in with my project.
Then I added the a target like this to my nant build script:
XML:
-
<target name="analyze" depends="your-target-that-builds-assemblies" description="Run FxCop against built assemblies">
-
-
<property name="fxcop.results.file" value="${build.dir}\fxcop-results.xml" />
-
<exec program="tools\fxcop\FxCopCmd.exe" failonerror="false">
-
<arg value="/file:${build.dir}\*.dll" />
-
<arg value="/file:${build.dir}\path\to\another\assembly\to\analyze.dll" />
-
<arg value="/forceoutput" /> <!-- create output even if no violations are found -->
-
<arg value="/ruleid:-Microsoft.Globalization#CA1300" /> <!-- an example of how to suppress rules -->
-
<arg value="/ruleid:-Microsoft.Globalization#CA1301" />
-
<arg value="/ruleid:-Microsoft.Globalization#CA1302" />
-
<arg value="/ruleid:-Microsoft.Globalization#CA1303" />
-
<arg value="/ruleid:-Microsoft.Globalization#CA1304" />
-
<arg value="/ruleid:-Microsoft.Globalization#CA1305" />
-
<arg value="/ruleid:-Microsoft.Globalization#CA1306" />
-
<arg value="/out:${build.dir}\fxcop-results.xml"" />
-
</exec>
-
</target>
And in your ccnet.config file, make sure you are merging the results file. Update your dashboard.config file if necessary. These changes are explained on the CC.NET Confluence site.
On my first pass with this, the output was not accounting for the violations I had suppressed in Visual Studio using the SuppressMessage attribute. The issue was that the SuppressMessage attribute is conditional. You need to define the CODE_ANALYSIS conditional compilation symbol in order for the attributes to be present in your built assemblies and therefore be noticed by FxCopCmd.exe.
Finally, if you're using FireFox instead of IE, you'll notice that the XSL presentation of the FxCop results are pretty ugly and hard to interact with. On the CruiseControl .NET Community XSL Transforms page, you'll want to grab fxcop XSLs from the Alternative Style Sheets and Templates Version 2.2, by Michael Luke. Thanks, Michael!
There's another approach, too, which is to call out to MSBuild to do the CodeAnalysis for you. You might achieve better integration with VS.NET that way. Can't speak to it, though, so you're on your own. If you take that path, leave a comment here and let me know how it turns out.
