This project is read-only.


ExcludeFromStyleCop cant be disabled / hidden


Is there a roadmap / uservoice / blog that provides information on oncoming features? I'm a bit surprised by the sudden arrival of ExcludeFromStyleCop.

Can it be changed to hidden by default
  • I don't want people using it
  • I don't want it taking up context menu real estate
What's the motivation for adding the feature when we could do it already within the file and avoid the other issue with it?

Closed Sep 20, 2013 at 9:39 AM by andyr
By design.


mightymuke wrote Sep 19, 2013 at 7:54 PM

ExcludeFromStyleCop hasn't suddenly arrived - it's been around for a long time. Don't use it if you don't want to. As stated in your other ticket, the preferred method now is to use File Lists.

mikeFourie wrote Sep 20, 2013 at 7:52 AM

Right I see its not new, thanks for the link. What I don't get is why this has been surfaced as a context menu item by default.

mikeFourie wrote Sep 20, 2013 at 10:25 AM

Can you define 'By Design'?

andyr wrote Sep 20, 2013 at 10:47 AM

Hi Mike - yes of course.

I design StyleCop

I wanted to add it.

mikeFourie wrote Sep 20, 2013 at 11:16 AM

Right, thanks for the constructive response.

andyr wrote Sep 20, 2013 at 12:29 PM

You're welcome - I would be happy to accept a changeset/fork adding the option if you'd like to contribute instead of just criticising. There's only me working on StyleCop part time.

mikeFourie wrote Sep 20, 2013 at 12:51 PM

Andy, take a step back and read my Issue. I'm asking questions. I do not see any criticism.


andyr wrote Sep 20, 2013 at 1:20 PM

Sorry Mike - you're right:

You used the words:
"I'm a bit surprised"
"I don't want people using it"
"I don't want it taking up context menu real estate"

And I thought you were being critical - my mistake.

Again, happy to take any code contributions instead of just asking questions.

mikeFourie wrote Sep 20, 2013 at 1:51 PM

Yes you are mistaken. Let me re-word it so its clearer.

I'm surprised that precious context menu real estate has been given to a feature which I expect to be used seldom. As well as taking up space and providing a continuous distraction, I do not want developers to see it and use it (they will abuse it). I would prefer that they fixed the issues or used other more appropriate methods to resolve them. I’ve managed to remove this option using VS, however I’d suggest reviewing the change or at least offering some insight as to why you think this is a good idea.

I don't have time to contribute to this project and I don't understand the criticism of 'asking questions'.


andyr wrote Sep 20, 2013 at 2:19 PM

The origin of the feature request for a context menu item is here -

mikeFourie wrote Sep 20, 2013 at 2:41 PM

Thanks I've pinged Caveman to try understand his scenario better.

mikeFourie wrote Sep 23, 2013 at 8:47 AM


Caveman's responded and as I suspected it's a useful feature to temporarily remove code during the adoption of stylecop. I'd still recommend File Lists as a better approach. Anyway, there is the whole other camp here who have a mature usage of Stylecop and even on legacy codebases, wouldn't use this. Can you add an option to remove this feature and preferably default it to off.