Feed Icon  


  • Bryant Likes
  • Send mail to the author(s) E-mail
  • twitter
  • View Bryant Likes's profile on LinkedIn
  • del.icio.us
Get Microsoft Silverlight
by clicking "Install Microsoft Silverlight" you accept the
Silverlight license agreement

Hosting By

Hot Topics


Open Source Projects



Cruise Control XSL

Posted in General | Test-Driven Dev at Wednesday, November 09, 2005 8:48 PM Pacific Standard Time

As I mentioned in my last post, we have relied heavily on CCNet on our project along with other open source tools. A couple other tools we use are NCover and FxCop. Both of these tools run as part of our NAnt build script along with NUnit. We display the results of these in our CCNet build report using custom XSL stylesheets. The stylesheets are all based on the NUnit stylesheet that comes with CCNet (which I also modified to correct a bug that happens when you have two methods with the same name) .

We also had to do some post processing on the NCover report to weed out some duplicate (and invalid) coverage details. I created another custom xsl which I used with msxsl.exe to transform the report into something more useful. If you run into this bug let me know and I'll post that stylesheet as well.



Monday, December 05, 2005 1:26:00 AM (Pacific Standard Time, UTC-08:00)
Hajo, I am trying to get Ncover working on .NET 2.0 wit nunit but NCover.Console.exe hangs. Do you know maybe what the proble is or maybe how to diagnose it?
<br>Pawel Pabich
Wednesday, February 08, 2006 12:58:00 AM (Pacific Standard Time, UTC-08:00)
Hi, I have problems with duplicates in the NCover report. Please put yours custom xslt for report postprocessing.
Tuesday, April 11, 2006 5:57:44 PM (Pacific Daylight Time, UTC-07:00)
Hi, I have problems with duplicates in the NCover report. Can you please put your custom xslt for report postprocessing.
Wednesday, September 13, 2006 11:43:04 PM (Pacific Daylight Time, UTC-07:00)
thank you very much, this xsls are great!
Monday, September 25, 2006 3:42:34 AM (Pacific Daylight Time, UTC-07:00)
Thanks for the FxCop XSL file, Brian.
Thursday, September 27, 2007 1:37:23 AM (Pacific Daylight Time, UTC-07:00)
Hi! I'm some kind of newbie in CCNet WebDashboard and i want to know, how can i use this files into mi report, because right now when I replace it... Booom! an exception is thrown by the CCNET Webdashboard.

Please help me in this.

Thanks a lot.
Friday, December 21, 2007 12:02:43 AM (Pacific Standard Time, UTC-08:00)
How do you attach the XSL to the XML? I get the following result:

NUnit Test Results
Assemblies tested: 0
Tests executed: 0
Passes: 0
Fails: 0
Ignored: 0

Assembly Test Details:
Wednesday, November 26, 2008 3:47:40 AM (Pacific Standard Time, UTC-08:00)
Thanks for the xsl man, it helps and saves a lot
Tuesday, January 13, 2009 11:18:29 PM (Pacific Standard Time, UTC-08:00)
@Dan: You probably using these xsl's for non CruiseControl result, like me :). I got also same result as yours, and realized that xsl is just for CruiseControl results.
Friday, January 23, 2009 12:33:45 AM (Pacific Standard Time, UTC-08:00)

I’ve been unable to integrate FxCop report in CC build report. I’m using CC 1.4.2 with FxCop 1.36. I was seeing build reports showing up in the ‘FxCop Report’ link. Then I changed it to the one provided by CC. Now I was seeing the page with FxCop Summary with all the metrics showing as zero and below that a blank FxCop Detail. I followed the CC document and configured all the other stuff - putting the xsl in xsl folder under webdashboard, updating dashboard.config with the path to FxCopReport.xsl and adding the path to the output xml after running FxCop in the ‘Merge’ block of ccnet.config. Can anybody help. Also if someone can email me a xsl that works and a screenshot of what the report is supposed to look like, I’ll know what to expect.



Friday, January 23, 2009 12:38:51 AM (Pacific Standard Time, UTC-08:00)
I was seeing build reports showing up whaen I was using the xsl provided by FxCop. Forgot to mention this in my previous post
Comments are closed.