Code Syntax Style: Optional Member Qualifiers
In C#, you can qualify instance members with this
keyword, and qualify static members with type name or a base type name. These qualifiers help you disambiguate members hidden by local variables or method parameters. In all other cases, these modifiers are optional, and you can decide for yourself whether to use them or not. With ReSharper, you can configure your preferences for using optional modifiers and enforce these preferences.
ReSharper helps you adjust optional member qualifiers 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.
In this topic:
- Enforcing preferences for optional member qualifiers
- Configuring preferences of optional member qualifiers
Enforcing preferences for optional member qualifiers
By default, ReSharper treats all optional member qualifiers as redundant and suggests removing them.

If you prefer to use optional qualifiers, you need to specify it explicitly as described below. For example, you may prefer to qualify static methods with the type where they are declared:

As soon as you change the preferences, ReSharper will treat the same code differently and suggest the corresponding corrections:

Another option to enforce preferences for member qualifiers in a bulk mode is code cleanup. You can either run code cleanup with the default profile Default: Full Cleanup or run the cleanup with a custom profile solely targeted at your specific task as described below.
To apply preferences for member qualifiers with code cleanup
- Open the Code Cleanup options: .
- Create a new profile as described in the Code Cleanup section. In the Selected profile settings section for the new profile, tick the Arrange qualifiers check box.
- Click Save 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 drop-down list. For more information, see Managing and Sharing ReSharper Settings.
- Select the scope where you want to enforce your preferences:
- Do one of the following:
- In the Code Cleanup dialog that opens, select the newly created profile.
- Click Run. ReSharper will enforce your preferences in the selected scope.
If you want to apply preferences for member qualifiers without opening the Code Cleanup dialog, you can bind the created profile to the silent cleanup and run it simply by pressing Ctrl+Shift+Alt+F. You can also create a custom cleanup profile that would combine applying the preferences with other code style tasks.
Configuring preferences of optional member qualifiers
Your member qualifiers style preferences are saved using the mechanism of shared 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.
To configure preferences for member qualifiers
- Go to the page of ReSharper options.
- Modify settings in the Instance member qualification and Static member qualification categories according to your coding practices/standards.
- The Notify with selectors in the right column allow you to set severity levels of code inspections detecting code that differs from your preferences.
- Click Save 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 drop-down list. For more information, see Managing and Sharing ReSharper Settings.
This feature is supported in the following languages/technologies:
See Also
Procedures:
- Naming Style
- Managing and Applying Code Formatting Rules
- File and Type Layout
- File Header Style
- Code Syntax Style: Namespace Imports
- Code Syntax Style: Implicit/Explicit Typing
- Using Auto-Properties
- Making Fields Readonly
- Code Syntax Style: Multiple Attributes
- Code Syntax Style: Modifiers
- Code Syntax Style: Optional Member Qualifiers
- Reformatting XML Doc Comments
- Removing Code Redundancies