"stylecop.violations" should be generated by StyleCop itself. It should output two files, "stylecop.xml" and "stylecop.violations.xml" from what I can remember.

The easiest way to debug this, is comment out all of the NAnt code regarding the number of violations. Just get StyleCop executing.

Once you've got that working, go to the StyleCop output directory you specified. This should be the variable {report.directory}. It looks like you have it set to D:. Check you have two xml files output there.

Alternatively you could use "stylecop.xml" I think, but you'd need to change the XSLT I've provided (for counting the violations) as the Schema may differ.

Hope that helps.

SORRY PREVIOUS POST HAD ERRORS

I have the following error:-

Unable to find source XML file 'D:stylecop.violations.xml'.

How is the stylecop.violations.xml file generated?

Should the command be changed from

09. arg line="-of ${report.directory}stylecop.xml"

to

09. arg line="-of ${report.directory}stylecop.violation.xml"

If not how is stylecop.violations.xml generated?

Thanks!

I have the following error:-

Unable to find source XML file 'D:stylecop.violations.xml'.

How id the stylevcop.violations file generated?

Should the command be changed from

09.

to

09.

If not how is stylecop.violations.xml generated?

Thanks!

If you look at the above snippets, you'll notice when "exec"ing StyleCop I specify an output directory for the report, "stylecop.xml". StyleCop will also generate a "stylecop.violations.xml file.

Now, using CruiseControl you should be able to write a template to display the data using XSL.

If you look in the directory where you installed CruiseControl.Net, you should notice a "webdashboard" folder. Inside that are all the templates, and XSLT's for transforming the XML data.

You need to:

1) Open up dashboard.config, look at the bottom, there should be an example of integrating additional reports into CruiseControl.Net. You'll have to have a play around with it.

2) Either write an XSL yourself to transform "stylecop.violations.xml" or download one (google around, I'm sure someone has written one).

I'd strongly recommend putting CruiseControl, namely the webdashboard and any .configs into source control.

1) The .resharper settings file is purely for ReSharper. It's what gets loaded with Visual Studio. You set this up to stop ReSharper writing messy, style-violating code.

2) UserSetting.xml is also related to ReSharper. It contains a user's specific settings, namely the "Code CleanUp" settings. These setting contain some StyleCop settings (ie how to clean up violations).

3) The Setting.StyleCop file is what the StyleCopForReSharper plugin reads. So whatever you have in there will match in Visual Studio, or if you ran StyleCop via commandline.

So far it matches virtually 95%. There are some odd cases, but on the whole it works virtually perfectly. It's just a matter of tweaking your StyleCop.Settings file, and .resharper settings file so that they work in harmony.

We have thousands of violations in our code, so even if it did only work 95% of the time, it still reduces the number of violations hugely each week.

The main trick is to enforce is as part of your continuous integration build. I've mentioned the troubles between comparing results on your local pc, to the build server towards the end of the article. It's something I want to fix in future.

I have few questions:

1. Does the Settings.StyleCop file matches exactly with resharper settings file?

2. Does the Enforcing results from StyleCop and resharper matches 100%.

The reason is, I want to make sure that the results on build server (using StyleCop) and on developer machine using resharper are the same.

Thanks

Rajesh