Code Inspections in Web.config
In Web.config, ReSharper 2017.3 provides two kinds of code inspections: 12 inspections that detect errors such as broken syntax, unresolved symbols, compiler errors, etc. (you cannot configure or disable any of these inspections), and 13 proprietary code inspections, any of which you can disable or change its severity level.
These code inspections help you detect code issues in design time in all open files, and additionally they allow you to find code issues in specific scope.
Configurable Web.config inspections are listed below, grouped by their categories.
Code Notification (2 inspections)
This category groups code inspections with minor severity levels.
| Ignored path || Disabled |
| Mapped path || Hint |
Potential Code Quality Issues (5 inspections)
This category includes inspections that detect critical issues (code smells), mostly with Error
level. This category also includes inspections that ensure localization assistance
| Cannot resolve module || Error |
| Cannot resolve symbol || Error |
| Module qualification required || Warning |
| Referenced path cannot be found in the website || Warning |
| Wrong module || Error |
Redundancies in Code (6 inspections)
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
| Redundant add element || Warning |
| Redundant add namespace element || Warning |
| Redundant element or attribute because of 'configSource' attribute || Warning |
| Redundant location element || Warning |
| Redundant remove or clear element || Warning |
| Redundant tagPrefix declaration || Warning |
Last modified: 23 January 2018