SA1633 Context menus appear when rule is Disabled

After disabling SA1633, StyleCop still presents the options Add StyleCop setting file to the project and Add file header to the Intellisense context menu. I’m more-so looking for a way to disable these menu items as I accidentally click them often. I do not use file headers, and I use .editorconfig to control all of my analyzer settings. However, I noticed both menus are both directly related to SA1633, so may be they should be hiding when this option is disabled.

This is the context menu items that still appear that I would like to disable. Both of these sub-menu items specifically call out SA1633.

[bjornhellander]

Alright, now I see it too. I was disabling the rule by using “Configure or suppress issues”/“Configure SA1633 severity”/“None” in that same context menu. When doing that, the severity is set to “none” in the .editorconfig file, but if I instead double-click on the .editorconfig file and set it to Disabled, the severity is set to “silent” which in my opinion is not a good thing. Silent means that the rule is executed and the diagnostic is reported, but it is simply not shown to you. But code fixes are still offered for diagnostics with severity silent, so that is why you keep seeing it in the content menu. I would say that this is a bug either in the compiler or in Visual Studio.

If you look at the .editorconfig file some other way (notepad, open with, etc), does it say “silent” for SA1633? If so, I hope that if you change silent to none, you will stop getting the context menu item about adding a header.

You will still be able to get the context menu item for adding the settings file in some situations, but it should in that case mention another rule. The reason for this is that the code fix for adding the settings file is configured to trigger on more rules than SA1633.

[sharwell]

Resolving as external