Define consistent coding styles with EditorConfig

To enforce consistent coding styles for everyone that works in a codebase, you can add an .editorConfig file to your solution or project. EditorConfig file settings adhere to a file format specification maintained by EditorConfig.org. Many code editors and applications support EditorConfig files, including Visual Studio. Because the settings are in a file, they accompany your code, and can be used even outside of Visual Studio.

In Visual Studio, EditorConfig file settings take precedence over the various global text editor settings available under Tools > Options > Text Editor > C/C++ > Code Style. You can use an EditorConfig file to tailor each codebase to use text editor settings that are specific to that project.

You can manually populate an EditorConfig file, or automatically generate it based on the code style settings you've chosen in Visual Studio. To create a new .editorconfig file based on your current Visual Studio settings, from the Visual Studio main menu choose Tools > Options > Text Editor > C/C++ > General. Then choose Generate .editorconfig file from settings. Choose the folder where your project is and then choose Select Folder to save the .editorconfig file.

When you use an EditorConfig file, you can still continue to set your own personal editor preferences in the Visual Studio text editor. These text editor settings apply whenever you're working in a codebase without an EditorConfig file, or when the EditorConfig file doesn't override a particular setting. An example of such a preference is whether to use tabs or spaces for the code indent style.

When you add an EditorConfig file to your project in Visual Studio, only new lines of code are formatted based on the EditorConfig settings. The formatting of existing code isn't changed unless you run one of the following commands:

• Code Cleanup.

  Select Code Cleanup in the Visual Studio editor, or press Ctrl+K, Ctrl+E. This command applies to white-space settings, such as indent style, and selected code-style settings, such as parenthesis preferences.

• Format Document.

  Select Edit > Advanced > Format Document, or press Ctrl+K, Ctrl+D in the default profile. This command applies only to white-space settings, such as indent style.

Code consistency

EditorConfig file settings let you maintain consistent coding styles and conventions in a codebase, regardless of the editor or IDE you use. Some coding styles you can control are indent style, tab width, end-of-line characters, and encoding. For example, if your C# codebase has a convention that indents use five space characters, documents use UTF-8 encoding, and lines ends with CR/LF, you can configure an EditorConfig file to use this convention.

EditorConfig files are useful when coding conventions you use on your personal projects differ from those conventions used on your team's projects. For example, you might prefer that an indent adds a tab character in your code. However, your team might prefer that an indent adds four space instead. EditorConfig files resolve this problem by letting you have a configuration for each scenario.

Because an .editorconfig file in the codebase contains the EditorConfig settings, they travel along with that codebase. As long as you open the code file in an EditorConfig-compliant editor, the text editor settings are activated.

Supported settings

The editor in Visual Studio supports the core set of EditorConfig properties:

• indent_style
• indent_size
• tab_width
• end_of_line
• charset
• trim_trailing_whitespace
• insert_final_newline
• root

EditorConfig supports all Visual Studio-supported languages except for XML support EditorConfig editor settings.

EditorConfig supports code style conventions including language, formatting, and naming conventions for C# and Visual Basic.

Add and remove EditorConfig files

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. For example, if the indents in your file are formatted with tabs and you add an EditorConfig file that formats indents with spaces, the indent characters aren't automatically converted to spaces. When you format the document (select Edit > Advanced > Format Document or press Ctrl+K, Ctrl+D), the white-space settings in the EditorConfig file are applied to existing lines of code.

If you remove an EditorConfig file from your project or codebase, you must close and reopen any open code files for the global editor settings to effect new lines of code.

Add an EditorConfig file to a project

To add an EditorConfig file to your project or solution, follow these steps:

1. Open a project or solution in Visual Studio. Select either the solution or project node, depending on whether your EditorConfig settings should apply to all projects in the solution or just one. You can also select a folder in your project or solution to add the .editorconfig file to.

2. From the menu, choose Project > Add New Item, or press Ctrl+Shift+A.

   The Add New Item dialog box opens.

3. In the search box, enter editorconfig.

   Two editorconfig File item templates are shown in the search results.

   

4. Select the editorconfig File (empty) template to add an EditorConfig file prefilled with default EditorConfig options for whitespace, code style, and naming conventions. Or, select the editorconfig File (.NET) template to add an EditorConfig file prefilled with default .NET whitespace, code style, and naming conventions.

   A new .editorconfig file appears in Solution Explorer, and opens in the editor as a new tab.

   

5. Optionally edit the file, and then save it.

Other ways to add an EditorConfig file

There are a couple of other ways you can add an EditorConfig file to your project:

• Use IntelliCode for Visual Studio to generate an .editorconfig file in your solution. Right-click in Solution Explorer and choosing Add > New EditorConfig (IntelliCode) from the context menu. IntelliCode for Visual Studio infers your code styles from existing code, and then creates an EditorConfig file with your code-style preferences predefined.

• Automatically generate an EditorConfig file based on your code-style settings.

File hierarchy and precedence

When you add an .editorconfig file to a folder in your file hierarchy, its settings apply to all applicable files at that level and lower. You can also override EditorConfig settings for a particular project, codebase, or part of a codebase, such that it uses different conventions than other parts of the codebase. Doing so can be useful when you incorporate code from somewhere else, and don’t want to change its conventions.

Follow these guidelines:

• To override some or all of the EditorConfig settings, add an .editorconfig file at the level of the file hierarchy you want those overridden settings to apply. The new EditorConfig file settings apply to files at the same level and files in any subdirectories.

  

• If you want to override some, but not all of the settings, specify just those settings in the .editorconfig file. Only those properties that you explicitly list in the lower-level .editorconfig file are overridden. Other settings from any higher-level .editorconfig files continue to apply.

• If you want to ensure that no settings from any higher-level .editorconfig files are applied to this part of the codebase, add the root=true property to the lower-level .editorconfig file.

  # top-most EditorConfig file for this level
  root = true
  

EditorConfig files are read from top to bottom. If there are multiple properties with the same name, the most recently found property with the same name takes precedence.

Edit EditorConfig files

Visual Studio 2022 provides a visual editor for EditorConfig files.

After you edit your EditorConfig file, you must reload your code files for the new settings to take effect.

Example

The following example shows the indent state of a C# code snippet before and after adding an EditorConfig file to the project:

1. In the Tools > Options dialog box, set the Text Editor > C# > Tabs settings for the Visual Studio text editor to produce four space characters when you press the Tab key.

   

2. As expected, when you press the Tab key on the next line, it indents the line by adding four white-space characters.

   

3. Use EditorConfig to switch the tabs setting to use tabs.

   Select Use Tabs in the EditorConfig file.

   

4. When you press the Tab key, tab characters now appear instead of spaces.

   

Troubleshoot EditorConfig settings

If an EditorConfig file exists anywhere in the directory structure at or above your project's location, Visual Studio applies the editor settings in that file to your editor. In this case, you might see the following message in the status bar:

User preferences for this file type are overridden by this project's coding conventions.

This means that if any editor settings in Tools > Options > Text Editor (such as indent size and style, tab size, or coding conventions) are specified in an EditorConfig file at or above the project in the directory structure, the conventions in the EditorConfig file override the settings in Text Editor.

To troubleshoot EditorConfig issues, follow these steps:

1. To turn off EditorConfig support for Visual Studio, clear the Follow project coding conventions option in Tools > Options > Text Editor.

   

2. To find any EditorConfig files in the parent directories of your project, open a command prompt and run the following command from the root of the disk that contains your project.

   dir .editorconfig /s
   

3. To control the scope of your EditorConfig conventions, set the root=true property in the .editorconfig file at the root of your repo or in the directory that your project resides.

   Visual Studio looks for a file named .editorconfig in the directory of the opened file and in every parent directory. The search ends when it reaches the root filepath, or if an .editorconfig file with root=true is found.

Related content

• Code-style rule options for .NET
• Supporting EditorConfig for your language service
• EditorConfig.org
• Features of the code editor
• Configuration files for code analysis rules