What updates to VS do we require to advance the analyzer eco-system?

[michaelcfanning]

1. We need a new ruleset editor.
2. We need new gestures for 'disable rule for all projects', etc.

[sharwell]

The following come to mind:

• It would be nice to configure built-in Visual Studio options alongside (or as part of) the analyzer configuration, so installation of an analyzer in the project also controls those Visual Studio options when working in the project.
• It would be nice if we could mark certain analyzers as mutually-exclusive. For example, when SA1101 is enabled, it doesn't make sense to have SX1101 or IDE0003 enabled (DotNetAnalyzers/StyleCopAnalyzers#530). In some cases this is more complicated due to partial overlap (DotNetAnalyzers/StyleCopAnalyzers#763), but I don't think we need to handle those cases.
• Currently analyzer dependencies are required to be listed as analyzers, even though they don't contain any diagnostics. These show up in Solution Explorer, and it's confusing to users. It would be nice to hide these in some way. For example see DotNetAnalyzers/StyleCopAnalyzers#1624, DotNetAnalyzers/StyleCopAnalyzers#1694, DotNetAnalyzers/StyleCopAnalyzers#1698.

[sharwell]

It would be amazing if the editor could treat string literals in analyzer tests matching particular patterns as embedded C# code (syntax highlighting, etc.).