When you add an EditorConfig file to your project or codebase, Visual Studio formats any new lines of code you write according to the EditorConfig file settings. However, Visual Studio doesn't convert existing styles to the new ones until you format the document or run Code Cleanup.

January 8, 2023 - # Top-most EditorConfig file. root = true # Section for C# files # All rules below apply only to .cs files [*.cs] #### Core EditorConfig Options #### # Indentation and spacing indent_style = space indent_size = 4 # New line preferences end_of_line = crlf insert_final_newline = false trim_trailing_whitespace = true # Charset preference charset = utf-8

EditorConfig files use an INI format that is compatible with the format used by Python configparser Library, but [ and ] are allowed in the section names. The section names are filepath globs (case sensitive), similar to the format accepted by gitignore. Only forward slashes (/, not backslashes) ...

December 1, 2025 - You can make changes in the preview ... when you close the .editorconfig file. Reformat your code. You can reformat a code fragment, a file, or all files in a directory. Alternatively, you can configure the IDE to reformat your code on save....

August 10, 2026 - JetBrains Rider will create or update the .editorconfig file in the specified location. You can also save formatting styles to EditorConfig after contextual configuration of formatting rules.

To create an EditorConfig file, you have a few options: Open your .NET project/solution in Visual Studio 2022. Click Tools > Options > Text Editor > C# > Code Style > General. Then click Generate .editorconfig file from settings.

November 27, 2024 - +---------------------------------------+----------------------------------------------------------------------------------------------------+ | Option | Description | +---------------------------------------+----------------------------------------------------------------------------------------------------+ | Add accessibility modifiers | Adds missing modifiers such as public or private | | Order modifiers | Sorts the modifiers in the correct order | | Remove unnecessary casts | Removes unnecessary casts that make the code more cumbersome to read | | Format document | Formats the document co

October 3, 2025 - As per title, the extension ignores "editor.formatOnSave": false, setting. Even when the property is off, the file (in my case, a .c file) is still formatted on save.

August 10, 2026 - By default, ReSharper writes the settings to a new .editorconfig file in the root directory of the current solution. If one or more .editorconfig files exist, ReSharper will use the closest file in the directory hierarchy to save the settings.

Extension for Visual Studio - Enables auto formatting of the code when you save a file. Visual Studio supports auto formatting of the code with the CTRL+E,D or CTRL+E,F key shortcuts but with this extension the VS command 'Format Document' is ...

July 23, 2017 - Hi, Using VS Code 1.14.2 with the latest editorconfig extension (0.9.4). Recently, it seems to have started auto formating on save. Because I use the save on delay option in VS code, this starts formating my code before I am done writing it.

April 8, 2026 - Extension for Visual Studio Code - EditorConfig Support for Visual Studio Code

Extension for Visual Studio - Automatically format document on save. Current release includes RemoveAndSort, FormatDocument, UnifyLineBreak, UnifyEndOfFile, TabToSpace, ForceUtf8WithBom with file extension filters.

Extension for Visual Studio - Automatically format document on save. Current release includes RemoveAndSort, FormatDocument, UnifyLineBreak, UnifyEndOfFile, TabToSpace, ForceUtf8WithBom with file extension filters.

December 4, 2024 - Also apparently you can run Code Cleanup profiles on Save: https://learn.microsoft.com/en-us/community/content/how-to-enforce-dotnet-format-using-editorconfig-github-actions#enforcing-code-style-on-save

EditorConfig files use an INI format that is compatible with the format used by Python ConfigParser Library, but [ and ] are allowed in the section names. The section names are filepath globs, similar to the format accepted by gitignore. Forward slashes (/) are used as path separators and ...

July 23, 2021 - I am using Visual Studio Code. EditorConfig extension for Visual Studio Code supports applying some of the rules(i.e. end_of_line insert_final_newline and trim_trailing_whitespace) on file save.

October 10, 2016 - You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert · {{ message }} There was an error while loading. Please reload this page. editorconfig / editorconfig-vscode Public · Notifications · You must be signed in to change notification settings · Fork 140 · Star 1.4k · New issueCopy link · New issueCopy link · Closed · Closed · Using "Format Code" feature ignores editorconfig settings after updating VS Code to 1.6.0#78 ·

It is equivalent to an .editorconfig file that contains only one line, root = false. Changed in version 0.15.0. A ; or # anywhere other than at the beginning of a line does not start a comment, but is part of the text of that line. For example: ... This specification does not define any “escaping” mechanism for ; or # characters. ... The EditorConfig file format formerly allowed the use of ; and # after the beginning of the line to mark the rest of a line as comment.