Hello, came across the error "Internal error in Requires any code files being checked in must pass the project code formatting guidelines .. Object reference not set to an instance of an object"
Id #7712 | Release:
| Updated: Thu at 10:25 AM by SergiiSA | Created: Thu at 10:25 AM by SergiiSA
SA1111 and SA1112 are both listed as "ClosingParenthesisMustBeOnLineOfOpeningParenthesis"
on the 4.7 readability rules index page (http://www.stylecop.com/docs/Readability%20Rules.html).
Id #7711 | Release:
| Updated: Nov 18 at 5:46 PM by noobler | Created: Nov 18 at 5:46 PM by noobler
According to rule SA1623 a property with just a getter should start with "Gets the". However, this rule does not work correctly when the property overrides a property from a base class. The below ...
Id #7710 | Release:
| Updated: Nov 4 at 10:09 PM by adavis83 | Created: Nov 4 at 10:09 PM by adavis83
This simple bit of code causes a syntax error:
public class Test1
public struct Rect2
public float x,y,w,h;
public class TestClass
public Rect2 TrackPosition = new Rect2();
Id #7709 | Release:
| Updated: Aug 30 at 8:33 PM by ptit_tof57 | Created: Aug 28 at 12:46 AM by fasteddo
Is there any chance of a minor update to StyleCop to compile with the Visual Studio 2015 SDK so that the IDE integration can be used, even if C# 6 syntax isn't understood?
Id #7708 | Release:
| Updated: Oct 24 at 10:29 PM by foster1890 | Created: Jul 30 at 7:08 PM by martincostello
I'm running latest StyleCop version with Visual Studio 2013, NCrunch 2.15 and Windows 8 64 bits. It works well but sometime I have this error.
..\version.cs (1, 1): SA0001 : CoreParser ...
Id #7707 | Release:
| Updated: Jul 3 at 7:29 AM by abelman | Created: Jul 3 at 7:29 AM by abelman
Allow project relative paths as SourceFile values in order to modify applied StyleCop rules for specific files.
SourceFile values are compared only against the file names of...
Id #7706 | Release:
| Updated: May 30 at 4:26 AM by fscottg77 | Created: May 30 at 4:25 AM by fscottg77
An "enum" with default scope is implicit "internal". However, StyleCop treats it like it is public and hench causes SA1600/SA1602, which disapears if the scope "internal" is specified explicit.
Id #7705 | Release:
| Updated: May 22 at 8:42 AM by MartinLorensen | Created: May 22 at 8:42 AM by MartinLorensen
The StyleCop Rules Guide (StyleCop.chm) appears to contain headings but no actual content.
Id #7704 | Release:
| Updated: May 27 at 4:06 PM by Rogedo | Created: May 20 at 2:39 PM by Rogedo
My team wants to leverage the C# 6 features which light up with the Visual Studio 2015 RC. Are there any plans to have StyleCop support these features?
Examples which break the StyleCop parser o...
Id #7703 | Release:
| Updated: Nov 11 at 1:23 PM by CrispinParker | Created: May 19 at 4:15 AM by thegalliano