ReSharper 2020.2 Help

Code Syntax Style: Modifiers

C# modifiers of types and type members can be written in any order. However, arranging them in a similar way throughout your code is a good practice, which improves code readability. Besides, you may prefer using or not using private and internal modifiers explicitly.

ReSharper helps you arrange modifiers in the existing code and takes your preferences into account when it produces new code with code completion and code generation features, applies code templates and performs refactorings.

Arrange modifiers in existing code

By default, ReSharper suggests to use private and internal modifiers explicitly, and to arrange modifiers in a specific order. If necessary, you can flexibly configure these preferences.

If your code does not comply with these preferences, ReSharper highlights such declarations and suggests the corresponding quick-fix or fix in scope for the order of modifiers:

Sorting modifiers

... for the private modifier:

Fixing implicit private modifier

... and for the internal modifier:

Fixing implicit internal modifier

Another option to enforce all your preferences for modifiers in a bulk mode is code cleanup. You can either run code cleanup with one of the default profiles Full Cleanup or Reformat & Apply Syntax Style, or create and run a custom profile solely targeted at your specific task as described below.

Apply preferences for modifiers with code cleanup

  1. Select ReSharper | Options from the main menu or press Alt+R O.

  2. Go to the cleanup profiles settings page: Code Editing | Code Cleanup | Profiles.

  3. Create a new profile as described in the Create a new custom cleanup profile section. In the Selected profile settings section for the new profile tick the Use explicit/implicit modifier for types, Use explicit/implicit modifier for type members, and Sort modifiers check boxes.

  4. Click Save in the Options dialog to apply the modifications and let ReSharper choose where to save them, or save the modifications to a specific settings layer using the Save To list. For more information, see Manage and Share ReSharper Settings.

  5. Select the scope where you want to enforce your preferences:

    • Set the caret anywhere in the file to enforce your preferences to the file.

    • Select one or more items in the Solution Explorer to enforce your preferences in the files under these nodes and their child items.

  6. Do one of the following:

    • Press Control+Alt+F or choose ReSharper | Edit | Cleanup Code... from the main menu .

    • Right-click anywhere in the text editor or right-click the selection and choose Cleanup Code in the context menu.

  7. In the Code Cleanup dialog that opens, select the newly created profile.

  8. Click Run. ReSharper will enforce your preferences in the selected scope.

If you want to arrange modifiers without opening the Code Cleanup dialog, you can bind the created profile to the silent cleanup and run it by pressing Control+Shift+Alt+F. You can also create a custom cleanup profile that would combine applying attributes style with other code style tasks.

Configure preferences for modifiers

Your modifiers-related preferences are saved using the mechanism of layer-based settings. Among other things, this mechanism allows you to maintain different preferences for different solutions as well as to keep these preferences under a VCS and automatically share them with your team members.

Configure preferences for modifiers

  1. Go to the Code Editing | C# | Syntax Style page of ReSharper options (Alt+R O).

  2. In the Modifiers category, specify the desired order of modifiers and set the preferences for explicit using of private and internal modifiers.

  3. The Notify with selectors in the right column allow you to set severity levels of code inspections detecting code that differs from your preferences.

  4. Click Save in the Options dialog to apply the modifications and let ReSharper choose where to save them, or save the modifications to a specific settings layer using the Save To list. For more information, see Manage and Share ReSharper Settings.

You can also change your preferences for explicit/implicit use of private and internal modifiers right in the editor, where corresponding issues are highlighted:

Change preference for modifiers in the editor

  1. Set the caret to a code issue highlighted by a ReSharper's inspection.

  2. Press Alt+Enter or click the action indicator to the left of the caret to open the action list.

  3. In the action list, choose Inspection "Use explicit or implicit modifier definition for types" | Prefer implicit 'internal' modifier :

    Changing the preference for explicit/implicit 'internal' modifier in the editor

  4. Your change will be saved using the smart save logic.

  5. If you need to save the modified style preference in a shared settings layer, click the Configure code style menu item or press Enter when it is selected. ReSharper will open the Code Editing | C# | Syntax Style page of ReSharper options (Alt+R O) where you can modify your preference as needed, click Save To and then choose the desired settings layer.

  6. In a similar way, you can change the preference for explicit/implicit private modifier.

    Changing the preference for explicit/implicit 'private' modifiers in the editor

This feature is supported in the following languages and technologies:

Language: C#Language: VB.NETLanguage: C++Language: HTMLLanguage: ASP.NETLanguage: RazorLanguage: JavaScriptLanguage: TypeScriptLanguage: CSSLanguage: XMLLanguage: XAMLLanguage: ResxLanguage: Build ScriptsLanguage: ProtobufLanguage: JSON
Feature is available in C#Feature is not available in Visual Basic .NETFeature is not available in C++Feature is not available in HTMLFeature is not available in ASP.NETFeature is not available in RazorFeature is not available in JavaScriptFeature is available in TypeScriptFeature is not available in CSSFeature is not available in XMLFeature is not available in XAMLFeature is not available in Resource filesFeature is not available in build script filesFeature is not available in ProtobufFeature is not available in JSON
Last modified: 03 September 2020