FR: Add an "all naming rule violations fixer"

[santo998]

Hi team,

When enforcing naming conventions using Roslyn analyzers (e.g., through Directory.Build.props or editorconfig), it's common to encounter many IDE1006 warnings (naming rule violations) — especially now that we're increasingly using AI-generated code, which might not always follow our project's naming rules.

For example, suppose I configured my IDE to enforce camelCase for private methods. If I write:

GetClient() {}
GetProduct() {}
InsertClient() {}
InsertProduct() {}

The IDE correctly raises IDE1006 for the four methods, since the names violate the rule. However, I can only fix them one by one via quick actions, which is very time-consuming when dealing with a large codebase.

Feature Request: It would be extremely useful to have the ability to apply all IDE1006 fixes in the current document, project, or solution — similar to how other refactorings or code cleanups work.

This would:

• Save time when enforcing naming conventions across a codebase

• Improve workflow automation

• Eliminate the need to spend tokens in AI prompts just to enforce syntax/naming preferences

• Make it easier to adopt naming rules consistently in projects

Is there any current workaround or plan to support this kind of bulk naming fix?
Thanks for considering this!

[josefpihrt]

Hi, I'm sure I understand. Could you be more specific please?

[santo998]

@josefpihrt done! TY so much.