-
This is not so much a feature, but would it be a big deal to get rid of all the "var" implicitly typed variables from the source code?
These were just added to accomodate linq and shouldnt be sprinkled throughout regular code haphazzardly.
They kind of look horrible, serve no purpose, they do not do much for code discovery, and make the code harder to understand and read.
2009-10-06 20:45:00 UTC by nobody
-
hi folks,
finally I got it working. This is an HOWTO:
Assuming you have successfully integrated StyleCopCmd with NAnt you are supposed to have two XML files (forget about any HTML files for CruiseControl.NET integration). In my case they are named stylecop.xml (this is the name you defined through the outputXmlFile attribute in your styleCopCmd element) and stylecop.violations.xml (forget...
2009-05-04 11:07:00 UTC by maotsetung
-
The -cs option does not work.
After I played around for almost a day, I inspected the source code. It turned out that there is a simple typo in the 'Main' function:
In Program.cs at line 47/48:
new StyleCopReport().ReportBuilder()
.WithStyleCopSettingsFile(cl.GetOptionValue("s"))
...
must be instead:
new...
2009-04-09 12:40:37 UTC by th-weller
-
I have *.cs in my csproj file:
This crashes the tool. Using -f *.cs also crashes with the same failure.
2009-04-06 15:05:17 UTC by nobody
-
I'm trying to do the same thing - did you get anywhere with this?
Thanks
Matt.
2009-04-01 00:21:10 UTC by maltin
-
This patch adds a "warningsAsErrors" attribute to the nant task that treats the stylecop violation warnings as errors to fail the build. The default is false, keeping the default behavior the same as it is now.
There is some question about how this should interact with the failonerror attribute. That attribute is ignored in this patch and will fail the build on a violation, regardless of...
2009-03-30 00:48:36 UTC by stevenjlyons
-
Hi,
Is it possible to integrate StyleCopCmd output with CruiseControl.Net?
I have successfully integrated StyleCopCmd within my NAnt build files
and it produces an .html and two .xml files. But I can't seem to be able
to display the result within CC.Net's dashboard. Any help is appreciated.
Thanks!
2009-03-04 04:32:02 UTC by robblixt
-
Probably it is better to point assemblies to Microsoft Installation dir.
May be NAnt and dotnetcli should not be referenced from StyleCop dir,
2009-01-22 13:02:46 UTC by packet7
-
If you try something like CustomSettings.StyleCop the --sc ignores your settings file.
2009-01-10 01:00:48 UTC by nobody
-
Tool returns exit code 0 always even if there are violations.
I think it should return -1 if there are violations.
If some people do not consider stylecop violations important they should ignore the exit code. For instance TeamCity has the option to ignore exitcode and consider the build successful.
2009-01-07 13:07:42 UTC by dipapadi
