Result: All documents will be formatted because we explicitly specified that all extensions will be formatted using allowed_extensions =. DefaultĮnable_in_debug = false Examples Scenario 1 You could explicitly configure to have the extension enabled while in a debug session. Defaultīy default the plugin is disabled in debug mode. For multiple values you could use space separated list.

Specifies all file extensions where the command is NOT allowed to be executed. Specifies all file extensions where the command is allowed to be executed. If you know how to reproduce this bug please log an issue. Note: In rare occasions VisualStudio2019 enters in a infinite loop. It is possible to replace the default command with Analyze.RunDefaultCodeCleanupOnSolution which executes all the commands configured in the default profile. Many people were asking how to execute a CodeCleanup on save. This is the Visual Studio command which will be invoked when a document is saved. There are 5 settings which you could configure: If possible, future versions of Visual Studio will be supported within this package.

Going forward this will be the version which will be supported and maintained. For that reason the extension is split into two: Visual Studio 2022 Since Visual Studio 2022 there are a lot of breaking changes in the VSIX SDK and it is really hard to support older versions of Visual Studio. Up until now the extension supported older versions of Visual Studio (2012-2019). Visual Studio supports auto formatting of the code with the CTRL+E,D or CTRL+E,F key shortcuts but with this extension the command Edit.FormatDocument is executed on Save. Enables auto formatting of the code when you save a file.

Visual studio auto format