Slow Analysis in ASP.Net Core Project

I realise it's a new technology, but thought I'd mention that StyleCop is quite slow doing a full project analysis on an ASP.Net Core v1 project. On the plus side, when it finishes the results are ...

Id #7747 | Release: None | Updated: Sun at 10:00 PM by Apogee | Created: Sun at 10:00 PM by Apogee

The rules set file is locked by visual studio

It seems that the style cop add-on locks the ruleset file so any attempts to override or edit it fail. This is a big problem when you want to provide a shared ruleset file between users and edit i...

Id #7746 | Release: None | Updated: Aug 15 at 6:57 AM by shkup | Created: Aug 14 at 9:34 AM by shkup

parsing of anonymous types fails in some circumstances

If my code contains the line var d = new {x = 1}; StyleCop cannot parse it and returns SA0102 ("A syntax error has been discovered"). Style cop does not attempt to continue working on that file....

Id #7745 | Release: None | Updated: Aug 11 at 9:05 AM by robertschwede | Created: Aug 11 at 9:05 AM by robertschwede

SonarQube 6.0 plugin

(Sorry, I thought I was writing in the "Discussions" section. Feel free to close this "issue") Hi, since SonarQube 6.0 the StyleCop plugin (http://docs.sonarqube.org/pages/viewpage.action?page...

Id #7744 | Release: None | Updated: Aug 8 at 7:26 PM by giacgbj | Created: Aug 8 at 7:24 PM by giacgbj

Exception:index was outside the bounds of the array

Hi: I get source code and when I debug it ,I found a bug . The filename :CodeLexer.cs Line::2068 else if (character == '?') { text.Append("?"); type = SymbolType...

Id #7743 | Release: None | Updated: Aug 3 at 3:17 AM by daoxingyue | Created: Aug 3 at 3:17 AM by daoxingyue

TeamCity build error

I get this build error on my TeamCity server, but not my local development box. Any ideas how to resolve? (I'm on 4.7.54) SA0001 : CoreParser : An exception occurred while parsing the file: System....

Id #7742 | Release: None | Updated: Jul 27 at 3:14 PM by ithi | Created: Jul 27 at 1:08 PM by ithi

SA1101: No warning for fields/properties that have the same name as the type

If a field/property has the same name as the type of the field/property, then StyleCop won't generate the SA1101 warning. Methods don't have this issue. If you use the full qualifier (e.g. instea...

Id #7741 | Release: None | Updated: Jul 26 at 2:51 PM by okl | Created: Jul 26 at 2:51 PM by okl

Crash StyleCop in VS 2015

I try to run Run StyleCop(Rescan All) in VS 2015 and project always crash. How can I resolve the crush?

Id #7740 | Release: None | Updated: Jul 25 at 2:04 PM by leapold | Created: Jul 25 at 2:04 PM by leapold

VS 2015 issue: Errors view does not show StyleCop issues

In VS2015 the new Errors view (that has been noticeably changed from VS2013) does not show StyleCop issues. Probably it is a pending issue to accomodate the warnings to be shown in this view. T...

Id #7739 | Release: None | Updated: Jul 28 at 3:28 PM by Ravelus | Created: Jul 19 at 3:58 PM by Ravelus

New rule SA1217 is incorrectly numbered

Rule SA1217, which for StyleCop Classic is first included in release 4.7.51, models the rule originally implemented in StyleCop Analyzers as SA1216. The identifier assigned to this rule should matc...

Id #7738 | Release: None | Updated: Jul 19 at 8:20 PM by probackpacker | Created: Jul 15 at 1:39 PM by sharwell