Settings

Read settings from editorconfig and project settings

If you use EditorConfig to maintain code styles for your project, you can also configure code inspections from .editorconfig files.

If this checkbox is enabled, you can configure code inspection severity levels and C# naming styles right from .editorconfig files.

Enable solution-wide analysis

Enables solution-wide analysis (including solution-wide code inspections), which is disabled by default.

Note that in large solutions, solution-wide analysis may result in some performance degradation. However, there are several ways to improve the performance of solution-wide analysis.

Enable computationally expensive inspections

Turns on the data-flow analysis and brings additional inspections, for example, to calculate nullability.

Monitor warnings

Enables warnings in solution-wide analysis.

When warnings are enabled in solution-wide analysis, it works as follows: as long as there are errors in the solution, only errors will be displayed; unresolved warnings will only appear when the last error is fixed. When warnings are disabled, the status bar indicator will turn green as soon as the last error is fixed.

When this option is enabled, you can click on the toolbar of the Errors/Warnings in Solution window to show or hide warnings in the window and in the status bar indicator without restarting the analysis.

Show unused non-private type members when solution-wide analysis is off

When this option is enabled, ReSharper will detect all unused non-private members even if solution-wide analysis is disabled. This option does not have any significant performance impact on small- and medium-sized solutions.

However, you may want to disable it if you experience performance problems in a large solution or when working with very large source files.

Show unused global using directives when solution-wide analysis is off

When this option is enabled, ReSharper will report all global using directives that reference unused namespaces even if solution-wide analysis is disabled. This option does not have any significant performance impact on small- and medium-sized solutions.

However, you may want to disable it if you experience performance problems in a large solution.

Value analysis mode

Using the value analysis, ReSharper finds out which entities can hold null value and highlights possible errors with null dereference. You can choose one of the following modes.

• Optimistic: when explicitly marked with [CanBeNull] attribute, or checked for null — ReSharper assumes that only entities explicitly marked with CanBeNull or ItemCanBeNull attribute or explicitly checked for being null, can be null.

• Pessimistic: when entity doesn't have explicit [NotNull] attribute — ReSharper assumes that all nullable entities without an explicit NotNull or ItemNotNull attributes can be null.

Nullable reference types' warnings mode

If nullable reference types (NRT) are enabled, ReSharper reuses the results of C# compiler analysis.

NRT improve overall precision of the nullability analysis, but there are cases when NRT contracts can be violated, for example when values are coming from code without #nullable context. In such cases you may get false positive warnings for nullability checks (for example, Expression is always 'true' or 'false') . In such cases, you can choose to ignore nullable API contracts and only report such cases when previous operations with the value in your code guarantee that it can or cannot be null.

For more information, see Nullable reference types.

Analyze integer arithmetic

Use this checkbox to enable or disable the analysis of integer values (integral arithmetics).

Color identifiers

This option lets you enable or disable ReSharper syntax highlighting scheme.

If it is selected, language identifiers are highlighted with colors as defined in Visual Studio options: Tools | Options | Environment | Fonts and Colors.

The list of syntax identifiers provided by ReSharper is available in the Display items list, each name starting with the ReSharper prefix.

Note that by disabling this option you also disable symbol information tooltips that appear on mouse over.

note

This option does not affect C++. To toggle syntax highlighting in C++, use the corresponding option on the Code Editing | C++ | Inspections page of ReSharper options .

Highlight color usages

Enables highlighting of color definitions in code. For more information, see Color assistance.

Highlight special characters in string literals

Enables highlighting of correct and incorrect escape sequences in non-verbatim strings. For example:

For more information, see Regular expressions assistance.

Highlight context exits

This option, which is enabled by default, tells ReSharper to highlight all places where the control flow can exit the current context. For example, for a method, it will highlight the return type of the method, all return, throw keywords, and so on when you set the caret to one of these identifiers

For a loop, it will additionally highlight the loop keyword as well as all the break statements inside this loop.

Note that if a method is not entirely visible in the editor, you can invoke the Navigate To Function Exits command on the method name to trigger another kind of highlighting, which will not disappear when your caret leaves the method name.

Highlight related async/await keywords

This option enables highlighting of all async and await keywords in a function when your caret is on one of them.

note

Newer versions of Visual Studio provide the same functionality, so it can still work even if you disable this option.

Highlight condition elements

This option enables highlighting of matching logical and conditional operators (|, ||, &, &&, as well as ? and ? pairs) that work together in a complex expressions when your caret is at one of such operators.

In the example below, %product helps understand that the highlighted operators will be evaluated together, while the value1 > 1 || value2 >= 2 && condition1 part will be evaluated before, and the || value6 %lt; value7 || condition2 part will be evaluated after, according to the operator precedence.

Use parallel code analysis when applying fixes/actions in scope

Use solution-wide analysis results when applying quick fixes in scope