Roslyn: Need 'fix-all' for naming style violations.

[CyrusNajmabadi]

It's just too tedious to have to manually fix up every violation one at a time.

[Pilchie]

Clearing milestone - this is not an RC issue.

[Pilchie]

Tagging @dpoeschl and @kuhlenh have either of you given any thought to this? Should it just be a blanket "fix all my names everywhere", or should it depend on which rule matched, etc?

[kuhlenh]

@Pilchie -- I believe we were thinking of having a "one-click cleanup" button for this (which would fix all formatting and name/style violations).

[CyrusNajmabadi]

I would like both options. One to fixup everything. And one to fix that specific violation.

[jnm2]

Same! Almost every event handler I've ever written has been camel case. I'd like a way to update an entire solution. :D

[jnm2]

I'm still blowing so much time on fixing these and then running into more.

[Mmatiasn]

I would love to help but where do I start?

[kendrahavens]

Duplicate from developer community

[sharwell]

I've had some thoughts about at least a _partial_ fix all implementation, but haven't completed it yet. For example:

1. If two code elements that need to be renamed are not visible in each other's scopes, it should be possible to rename both of them in a single operation without conflicts.
2. If two variables in a shared scope have distinct names before and after the fix, and neither of the fixes applied individually has any conflicts, then it should be possible to rename both of them in a single operation without conflicts.
3. Rules 1 and 2 should hold for any number of identifiers

[artemious7]

I'd be happy to see this implemented too.