FxCop graph
The FxCop graph stylesheet generates a graph showing FxCop results for all measured assemblies in the current build.
I'm interrested in your feedback on the stylesheet, so please create comments!
Originally developed at Kamstrup, but made avilable to the CruiseControl.NET community.
Installation
Copy the FxCopGraph.xsl file to the webdashboard\xsl directory.
Add the following code to the dashboard.config file:
<xslReportBuildPlugin description="FxCop Graph" actionName="FxCopGraph" xslFileName="xsl\FxCopGraph.xsl">
<includedProjects>
<projectName>MyProjectName</projectName>
</includedProjects>
</xslReportBuildPlugin>
Where MyProjectName is the name of the project where graph should be available.
Hello,
Thanks for sharing !
Maybe you can help me out on the original fxcop report stylesheet?
During an analysis of multiple assemblies , fxcop creates remarks on several assemblies. Unfortunately , the dashboard only shows the results of one single assembly. It seems to ignore the other assemblies as mentionned in the fxcop analysis. I can see evidence of the analysis in the build log of CCNet.
I'm using CCnet 1.3 and Fxcop 1.35
Thanks in advance.
Regards,
Alexander
halo all..
Can u help me by saying how we can integrate FxCop in ccnet.config ?
</exec>I've had good luck with this. FxCopWrapper.exe, my own application, simply calls FxCopCmd.exe with the buildArgs and returns 0 (success for the <exec> process). My FxCop projects still errs for reasons I have yet to figure out and that's why I created the wrapper project. I'm also much more interested in the output than the fact that it erred because it couldn't load some Crystal Report assembly...
Using FxCopCmd.exe instead of my FxCopWrapper.exe worked but the return codes caused my builds to fail.
By the way, my previous post looked much better in the viewer...
Very good job, thanks.
Hi,
I have greatly enjoyed setting up cruisecontrol and associated reports. Thanks to all who have made this tool and associated reports possible.
I appear to have an issue with errors reported by FxCopGraph and FxCopReport.
FxCopGraph reports 20%-25% more errors than FxCopReport when run over the same project in the same build. Could you please clarify if this is a bug and which of the report is correct.
Thanks
lakshman
I am using CCNet 1.2.1.7 & FxCop 1.35
Hello. I'm not working at Kamstrup anymore and therefore not working with the report anymore. Fell free to fix any bugs and upload a new version.
Comment to Alexander Nowak:
Did you find any solution to the stripped output in the webdashbord? I'm having the exact same problem with FxCop 1.35. Only the first assembly is listed. Though the FxCopGraph.xsl actually shows for all assemblies...
Comment to Austin Salongen:
I had a similar problem my self. Turned out to be the project being kind of strong-typed against the types that existed while the FxCop project was created. So refactoring and renaming types in source made the analyzation process return error because some types were now 'missing' / renamed. The solution to this problem is to add the '/u' flag to the FxCopCmd to have it update the project file.
Hello Bjorn,
I used the XSL stylesheets from Bryan likes on http://blogs.sqlxml.org/bryantlikes/archive/2005/11/10/4480.aspx
I did have some troubles with the image references though but I changed them. It works fine now for me.
Hope this helps.
best regards,
Alexander
ps : You contact me on my email if you need. I don't keep a close eye on this site.