Finding Code Issues with Code Inspection
Static code analysis in ReSharper is called Code Inspection and performed by applying over 1400 individual code inspections to your code in all supported languages.
Code issues can be found in several ways:
- ReSharper finds and highlights code issues automatically in design time for all files opened in the editor. The design time code inspection scope can be extended to the entire solution - in this case, you will be able to see all errors in the solution and some additional issues in the opened files, e.g. unused public members.
- You can find code issues in the specified scope, which can be as large as the whole solution.
- You can also find code issues from the command line.
You can extend the default set of code inspections with structural search and replace patterns, and get more inspections for specific purposes (e.g. spell-checking inspections) by using ReSharper extensions.
In this section:
- Code Inspections
- Detecting Code Issues in Design Time
- Finding Code Issues in Specific Scope
- Solution-Wide Analysis
- Configuring Code Inspection Settings
- Creating Custom Code Inspections and Quick-Fixes
- Value and Nullability Analysis
- Code Analysis and Helpers for String Literals
- Using Annotations to Refine Code Inspection
This feature is supported in the following languages/technologies:
C# | VB.NET | C++ | HTML | ASPX | Razor | JavaScript | TypeScript | CSS | XML | XAML | RESX | Build Scripts | Protobuf | JSON |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
The instructions and examples given here address the use of the feature in C#. For details specific to other languages, see corresponding topics in the ReSharper by Language section.