Code Analysis tooling issues with editorconfig

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

With the new way of implementing Code Analysis for .NET 5 and 6, as described in https://docs.microsoft.com/en-us/dotnet/fundamentals/code-analysis/overview, there are few regressions from the tooling point of view:

• it's not possible to easily select all available rules, for example to make all of them as warning;
• it's not possible to search for rule code or text (for example, all rules about "async" or "dispos")

These features were available with the old ruleset editor. It would be cool if they could be reintroduced for the new editorconfig and globalconfig files.

---

Original Comments

(no comments)

[jmarolf]

Half of this has been addressed in https://github.com/dotnet/roslyn/pull/57188. Previously the search bar blended into the tool window 😞. The new UI now looks like this:

Multi-select, however is an important productivity enhancement and I'll use this issue to track that.

[curia-damiano]

Thank you @jmarolf for tracking this!