I had to restart IIS. Once restarted, this started to work without any additional changes.
-----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Rayment Sent: Friday, August 29, 2008 12:25 AM To: [email protected]; [EMAIL PROTECTED] Subject: [ccnet-user] Re: Issue with FxCop 1.6 and FxCop task in MSBuild.Community.Tasks As it happens I set up FxCop 1.36 with CC.NET this afternoon. I used the style sheets from: http://lokad.svn.sourceforge.net/viewvc/lokad/integration/FxCopReport.xs l http://lokad.svn.sourceforge.net/viewvc/lokad/integration/fxcop-summary. xsl I had a problem with the images. I found that CC 1.4 has the necessary images in the webdashboard/images folder but the path wasn't correct in the xsl. If you change all elements referencing images from: <input type="image" src="/../images/arrow_plus_small.gif"> to <input type="image" src="/ccnet/images/arrow_plus_small.gif"> then it all works as intended. I think the issue here is how you have IIS configured and where the root is. Our setup at work uses the default settings as installed so should work for the majority... Kind regards, Tim -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Desai, Anand Sent: 28 August 2008 06:38 To: [email protected]; [EMAIL PROTECTED] Subject: [ccnet-user] Re: Issue with FxCop 1.6 and FxCop task in MSBuild.Community.Tasks Hi, I don't have this problem. For me, FxCop 1.36 is working. It is generating the report as well. However, I see following 2 problems: 1. The report is either not merged properly or something else. For one project, FxCop results are not showing up. 2. For other reports, they are showing up and I use xsl suggested in previous post which solved the hang up problem. But, the xsl is referring to some images which are missing and the report doesn't look pretty. Can someone guide me in the right direction? The original post doesn't mention anything about images or css to resolve this issue. Thanks, Anand -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of si Sent: Thursday, August 28, 2008 10:46 AM To: [EMAIL PROTECTED]; [email protected] Subject: [ccnet-user] Issue with FxCop 1.6 and FxCop task in MSBuild.Community.Tasks Greetings, Apologies for the cross-post, but I figured both lists may be interested... Just upgraded our CruiseControl.NET 1.4 server with FxCop 1.36 after uninstalling FxCop 1.35. We use the FxCop task in the MSBuild.Community project, and unfortunately this task no longer works. A peek at the source in FxCop.cs task suggests the registry key has (probably) been changed between 1.35 and 1.36. Quick and dirty fix is to manually create a registry key: HKEY_CLASSES_ROOT\FxCopProject\shell\open\command With default value of: "c:\Program Files\Microsoft FxCop 1.36\FxCop.exe" "%1" As to a more permanent fix, once approach might be to check if key FxCop.Project.9.0 exists, and if it does, use that before falling back to FxCopProject. -- It's a wild world that we live in, you step to the vibe like a new found religion, take your position, compile your vision, futurism, algorithm has risen up! pfm - the western ======================================================================== ==== == Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ======================================================================== ==== == ============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ==============================================================================
