This page of ReSharper options displays all ReSharper's code inspections grouped by languages and categories, and allows you to change the severity levels that ReSharper assigns to issues found by each inspection.
Note that this page only lists inspections that have configurable severity levels. There are also hundreds of inspections that detect compiler errors, which have fixed Error severity level and they are not shown here.
Code inspections are arranged into several categories:
Potential Code Quality Issues
This category includes inspections that detect critical issues (code smells), mostly with Error or Warning level. This category also includes inspections that ensure localization assistance.
Common Practices and Code Improvements
This category groups inspections that hunt for medium severity issues that mainly affect code readability.
Redundancies in Code
Code inspections in this category look for redundancies and dead code, which affect code readability and style, and could be safely removed. Some code redundancies cannot be fixed automatically, and quick-fixes for them are performed in the interactive mode, requiring the user input. But the majority of the redundancies can be fixed without user interaction, using either fix in scope or code cleanup. For more information, see Removing Code Redundancies.
Language Usage Opportunities
This category includes code inspections, mostly with the suggestion severity level, which notify you when more advanced language constructs can be used. In C#, these inspections detect syntax of outdated C# versions and suggest using features from more modern language versions up to C# 6.0 and partially C# 7.0. By default, ReSharper automatically detects C# version based on the associated compiler. However, you can specify the target C# version explicitly by selecting the project in the Solution Explorer and using the C# Language Level property in the Visual Studio's Properties window (choose in the menu).
This category groups code inspections that mostly detect errors and warnings in web projects.
Inspections in this category detect violations of code style rules. In contrast to the rest of code inspections, these inspections can either detect the same code construct as a code issue or not depending on the corresponding code style rule configured in the pages of ReSharper options. You can also fix issues that these inspection detect, using code cleanup. For more information, see Code Style and Cleanup.
This category includes code inspections, mostly with the warning severity level, which detect violations related to symbol attributes, including ReSharper's code annotations, and other similar issues.
Redundancies in Symbol Declaration
This category includes code inspections, mostly with the warning severity level, which detect empty and unused symbol declarations.
Inspections in this section detect compiler warnings before you compile.
These inspections detect code issues related to NUnit tests.
If the default severity level of an inspection is changed, you will see the
Reset to default
button next to it, which allows you to reset the severity
to its default value.
The same button also appears next to the category where such inspection belongs, Clicking this button next to a category will reset all inspections inside the category to their default severity levels.