Comments on: Using FxCop 1.36 with CruiseControl.Net

By: Adel

Adel — Sat, 24 Jan 2009 05:20:26 +0000

Sorry for some reason, its not showing some stuff. I can email it

By: Adel

Adel — Sat, 24 Jan 2009 05:19:11 +0000

Sorry my post didn’t come out right. NAnt block is following

also it missed the first few lines of the xml

Analysis Report
#Title {font-family: Verdana; font-size: 14pt; color: black; font-weight: bold}
.ColumnHeader {font-family: Verdana; font-size: 8pt; background-color:white; color: black}
.CriticalError {font-family: Verdana; font-size: 8pt; color: darkred; font-weight: bold; vertical-align: middle; }
.Error {font-family: Verdana; font-size: 8pt; color: royalblue; font-weight: bold; vertical-align: middle; }
.CriticalWarning {font-family: Verdana; font-size: 8pt; color: darkorange; font-weight: bold; vertical-align: middle; }
.Warning {font-family: Verdana; font-size: 8pt; color: darkgray; font-weight: bold; vertical-align: middle; }
.Information {font-family: Verdana; font-size: 8pt; color: black; font-weight: bold; vertical-align: middle; }

.PropertyName {font-family: Verdana; font-size: 8pt; color: black; font-weight: bold}
.PropertyContent {font-family: Verdana; font-size: 8pt; color: black}
.NodeIcon { font-family: WebDings; font-size: 12pt; color: navy; padding-right: 5;}
.MessagesIcon { font-family: WebDings; font-size: 12pt; color: red;}
.RuleDetails { padding-top: 10;}
.SourceCode { background-color:#DDDDFF; }
.RuleBlock { background-color:#EEEEFF; }
.MessageNumber { font-family: Verdana; font-size: 10pt; color: darkred; }
.MessageBlock { font-family: Verdana; font-size: 10pt; color: darkred; }
.Resolution {font-family: Verdana; font-size: 8pt; color: black; }
.NodeLine { font-family: Verdana; font-size: 9pt;}
.Note { font-family: Verdana; font-size: 9pt; color:black; background-color: #DDDDFF; }
.NoteUser { font-family: Verdana; font-size: 9pt; font-weight: bold; }
.NoteTime { font-family: Verdana; font-size: 8pt; font-style: italic; }
.Button { font-family: Verdana; font-size: 9pt; color: blue; background-color: #EEEEEE; border-style: outset;}
a:link { color: blue; text-decoration: none; }
a:visited { color: blue; text-decoration: none; }
a:active { color: blue; text-decoration: none; }

By: Adel

Adel — Sat, 24 Jan 2009 05:13:35 +0000

As an added note to my previous post, I’m generating the xml fxcop output from my NAnt build script in the following way.

Looks like it is generating an html output with an xml extension. First few lines are following

function ViewState(blockId)
{
var block = document.getElementById(blockId);
if (block.style.display==’none’)
{
block.style.display=’block’;
if (block.className == ‘MessageDiv’)

notice the html starting tag.

Is anybody else experiencing this. Is there a way to tell FxCop not to generate the html file. I’m thinking this could be the reason why my page is not showing up right.

By: Adel

Adel — Fri, 23 Jan 2009 16:23:09 +0000

I’ve been unable to integrate FxCop report in CC build report. I’m using CC 1.4.2 with FxCop 1.36. I get what some of the guys were getting trying to use the xsl provided by FxCop-build reports were showing up in the ‘FxCop Report’ link. Then I changed it to the one provided by CC. I’m getting something different (not just the first assembly showing up) – I was seeing the page with FxCop Summary with all the metrics showing as zero and below that a blank FxCop Detail. Then I tried with the xsl provided by Ben and I was getting a totally blank page. 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 screenshot of what the report is supposed to look like, I’ll know what to expect.

Thx
Adel

By: Trev

Trev — Wed, 29 Oct 2008 02:34:03 +0000

Hi Ben,

Thanks a lot for sharing this with everyone. It makes such a big difference. Your contribution to the community is very much appreciated!

Trev

By: Barry

Barry — Fri, 22 Aug 2008 17:38:59 +0000

Hi,

Just wanted to add my thanks for this!

Barry

By: Vishal Patil

Vishal Patil — Fri, 11 Jul 2008 15:04:37 +0000

Hi Ben,
This xsl helped a lot to me. All the other contributions to FxCopReport so far for all the previous and current version of FxCop were not working for me. For some xsl the webdashboard of ccnet showed me the build summary and some showed me only Expan and Collapse buttons. But the xsl by you worked very well. Thanks a lot.

Thanks onec again.
Vishal Patil 91-9373141426, Pune, India.

By: Daniel Hommel

Daniel Hommel — Sun, 09 Mar 2008 21:04:05 +0000

Ben,

i’m a contributor to CCNET and i’d like to recommend your modified XSL file for inclusion in the 1.4 release.

If you are interested please drop me a line.

regards,

Daniel

By: harish

harish — Wed, 05 Mar 2008 23:58:49 +0000

That was very helpful , saved tones of time mucking around the default fxcopreport xsl which comes with ccnet.

thanks =)

By: James G

James G — Fri, 22 Feb 2008 09:54:25 +0000

Awesome dude, was looking through useless guide after useless guide, none of the top google listed results have working guides for the latest versions!

Nice one.