Starting in Visual Studio 2022 17.1 Preview 2, developers can now perform Code Cleanup automatically when a file is being saved! Code Cleanup automatically on Save is a new feature integrated into Visual Studio 2022 that can clean up your code file to make sure it is formatted correctly and that your coding style preferences are applied. Some customizable preferences include: format document, sort usings, remove unnecessary usings, and more. This feature can help minimize stylistic violations within PRs and more to allow developers to spend less time fixing code not meeting specific standards and more time doing what they do best. To give it code cleanup on save a try, download Visual Studio 2022 Preview:
How to enable Code Cleanup on Save
First, navigate to Analyze > Code Cleanup > Configure Code Cleanup to personalize desirable customizations to your code cleanup profile(s).
Next, navigate to Tools > Options > Text Editor > Code Cleanup. Add a check in the “Run Code Cleanup profile on Save”. Be sure to select the appropriate profile you want to execute automatically whenever you save!
Try it out and share your feedback!
We would love to get your feedback on Code Cleanup on Save so please give it a try and let us know what you think! You can share any feedback via Developer Community to help us make Visual Studio better for you!
Hi, I do not know if it is asked before. Is there a way to add a 3rd or 4th profile? I have been already using these profiles, now I need to add new profiles to use in specific cases. Thx in advance.
I’m not seeing Code Cleanup under my Text Editor settings in Visual Studio 2022 version 16.11.10
I also have Resharper installed. Could that be conflicting with this somehow?
I am able to run code cleanup, but would love to set it to automatically occur on save.
Update your VisualStudio version to 17.1, after that Code Cleanup will be visible.
I just checked, and apparently Resharper has its own cleanup on save options.
That is great, I used the “Format document on Save” extension to do this.
Will there be a way to save without formatting? This is something the developer added to that extension, and that is also available in vscode.
Is there a risk of this breaking stuff?
I note the demo removed "unusedVariable" - what if that wasn't "unusedVariable", but "soonToBeUsedVariable"?
Does this also do some of the automagic fixes that Ctrl+. comes up with? I've had some strange things from there where the fix has removed half of the line to meet some "Hey! This is a good idea!" rule, but has just messed the line up.
Related, does it do the automatic "You changed X to Y in half the document - do you want to do it here?" suggestions? Sometimes useful, sometimes not - if I copy the...