tabs are nog allowed


I chose to hide 'tabs are not allowed' option SA2017 and still stylecop complains that I should not use tabs instead of spaces. I don't care what YOU think my code should look like, but what I WANT the code to look like and be organized. I disabled half the rules so far since they're personal or completely not applicable.


Style cop is to be an assistant that helps maintain code consistency and not enforce the MS rules by default. I don't care what MS thinks the rules should be, I on the other hand use my brain myself and CHOOSE not to following them blindly. It's not because MS desided to change the conventions every 3 years, that I should follow them blindly. Why else would they allow variations on their own settings and I hold strong to the KLR settings invented by IBM years ago.I find that style to be the most complete and as susch I don'ty need some shit plugin to tell me that everything I do is wrong.
  1. I use _PascalCase for my privatte fields
  2. I place all properties together with their backing fiield in a separate region (1region=1 property + 1 backingfield + additional property taginfo)
  3. I structure all my files in the same order
  4. I HATE file header since they only take up space that I can use for other purposes and they tend to get out of sync with the rest of the file summary.
  5. I refuse to use the c#alias since a type should look the same weither it's built in or no. I want all my types to be the REAL .NET types (Int32, Boolean, String, ...)
all these options are not available or not working properly due to incosistent testing (expect the property-field combo which can't be tested, but should be ignored)
Closed Dec 1, 2016 at 4:15 AM by csdahlberg


Przemyslaw wrote Oct 31, 2014 at 9:21 AM

Since StyleCop's exact purpose is to enforce MS code style rules, it looks like you are not a target of this plugin. StyleCop isn't (and never intended to be) general and customizable code style plugin. If you don't like it, don't use it. I don't understand your whining.

d4e666 wrote Oct 31, 2014 at 10:27 AM

  1. stylecop is an extension to Reshaper so if the only purpose is to enforce MS policy, why pluing into Resharper. VS2012 already has plugins for this purpose
  2. Resharper DOES allow deviation of the standards to respect THAT choice
  3. StyleCop does have some features I like (like forcing filled comments)
  4. when I set some options to 'don't show' why do they still get enforced. Why would I not want to see rules that get enforced behind the scenes. Now I have over 1000 'warnings' not showing in my files, but that are listed. This makes no sense.
and most important: if you create a plugin for Resharper, you should at least respect THEIR choices, otherwise kill your plugin and write plugins for Visual Studio instead, so who's whining now? Me that respects the choices of Resharper or you that abuses their software to crawl op MS ass.

PS; the MS naming convention is usefull, but it's up to the developer to choose his own. Some rules should not be enforced but rather be considered 'sugestions' like starting private fields with underscore -> I do this so that I see the difference between my properties and fields more clearly. lower case fields are easaly read over during code reviews and error tracing. Words starting with underscores are more easaly spotted as 'not being correct'

SkipIsHere wrote Dec 9, 2014 at 12:12 PM

d4e666 you do realise that StyleCop is NOT a plugin for Resharper, it is a separate tool. (You can install StyleCop and run it without Resharper, this is how I currently use it at home)

The pluggin aspect is so that it integrates with Visual Studio to give you the lovely green squiggles, it sounds like the settings for Resharper and StyeCop are not in sync. (Which is how I use it at work)

csdahlberg wrote Dec 1, 2016 at 4:15 AM

Happily closing this bug with extreme prejudice against d4e666.