Using Clang-Format

Select ReSharper | Options in the main menu or press Alt+R,O, then choose Code Editing | General Formatter Style on the left.

In the Code style configuration files section, click Write current style to .clang-format. This will open the Export to .clang-format dialog.

By default, ReSharper writes the settings to a new .clang-format file in the root directory of the current solution. If one or more .clang-format files exist, ReSharper will use the closest file in the directory hierarchy to save the settings. If necessary, you can change the destination file using the path selector at the top of the dialog.

For more detailed configuration, you can expand Show additional options and choose the following options:

• Export settings that have default values
  By default, ReSharper only saves properties for settings that you have changed. So only these settings will apply and override other settings when the resulting .editorconfig is read by ReSharper or Rider. All other settings will take values specified in the IDE.
  If you enable this option, ReSharper will save all settings in their current state, regardless whether they were changed or not. This way you will get a stricter .editorconfig that will override all code style and formatting settings when read by ReSharper or Rider.

• Remove existing properties with ambiguous values
  Some EditorConfig properties could correspond to multiple ReSharper-specific properties, which allow for a more precise configuration. So there could be situations when a more general property agrees with some related ReSharper-specific properties and contradicts to others, which makes this more general property ambiguous.
  As more detailed properties have higher priority, such a situation is not a problem and there is no need to remove properties with ambiguous values.
  The only case when you may want to remove properties with ambiguous values is when the project EditorConfig styles are going to be read only by ReSharper and Rider, and you want to remove redundancies from the .editorconfig file.

• Export standard .editorconfig properties — whether to save standard .editorconfig properties These properties will also apply if the generated EditorConfig is read by other editors and IDEs.

• Export cross-editor language-specific properties — whether to save .NET-coding-convention properties. These properties will also apply if the generated EditorConfig is read by other editors and IDEs.

• Export JetBrains Rider/ReSharper-specific code style properties — whether to save product-specific code formatting styles, code syntax styles.

• Export JetBrains Rider/ReSharper-specific inspection severities — whether to save severity levels for ReSharper's configurable code inspections.

• BasedOnStyle — sets the corresponding option to define which which style is used for all options by default.

• Hide options that coincide with the chosen base style
  Options that have the same value as defined in the base style that is selected in BasedOnStyle will not be exported.

• Export CPP settings — whether to export Clang-Format options that affect C++ code.

• Export CPP settings — whether to export Clang-Format options that affect JavaScript code.

If there is an existing .clang-format file in the specified location, there could be conflicts between values of properties that exist there and the ones that ReSharper is about to save. Such properties will be shown in red and if you proceed with saving, the conflicts will be resolved in favor of the newly generated ones.

Click Export. ReSharper will create or update the .clang-format file in the specified location.