In this page of JetBrains Rider settings, you can specify your preferences for code inspection.
Enable code analysis
Select this checkbox to enable design-time code inspection.
Regardless of this checkbox, you can always run code inspection in specific scope.
Read settings from editorconfig, project settings and rule sets
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.
This checkbox also enables reading code inspection severity settings from Roslyn Analysers Rule Sets. For more information, see Rule Sets format
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.
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 All Solution Files tab of the Problems tool window Alt+6 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, JetBrains Rider 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, JetBrains Rider will report all
However, you may want to disable it if you experience performance problems in a large solution.
Value analysis mode
Using the value analysis, JetBrains Rider finds out which entities can hold null value and highlights possible errors with null dereference. You can choose one of the following modes.
Nullable reference types' warnings mode
If nullable reference types (NRT) are enabled, JetBrains Rider 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
For more information, see Nullable reference types.
Analyze integer arithmetic
Use this checkbox to enable or disable the analysis of integer values (integral arithmetics).
This option lets you enable or disable syntax highlighting scheme.
If it is selected, language identifiers are highlighted with colors as defined in settings pages under thepage of JetBrains Rider settings Ctrl+Alt+S. in Visual Studio options: .
Note that by disabling this option you also disable symbol information tooltips that appear on mouse over.
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 JetBrains Rider 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
For a loop, it will additionally highlight the loop keyword as well as all the
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
Highlight condition elements
This option enables highlighting of matching logical and conditional operators (
In the example below, %product helps understand that the highlighted operators will be evaluated together, while the
Quick fixes and context actions
Use parallel code analysis when applying fixes/actions in scope
Use solution-wide analysis results when applying quick fixes in scope
Elements to skip
JetBrains Rider allows you to configure the list of files, file masks, and folders that should be excluded from code inspection. The excluded items are ignored by both design-time code inspection and code inspection in specific scope, but they are still indexed by JetBrains Rider, so that you can navigate to or refactor symbols excluded from code inspection.