JetBrains Rider helps you analyze code on various levels, starting from a single statement in the editor and all the way through to the architecture of your entire solution.
Finding code issues
By default, JetBrains Rider starts analyzing a code file as soon as you open it in the editor, all the way you edit it, until it is closed. This design time inspection is performed silently by continuously applying all code inspections to your code. Not only JetBrains Rider highlights code issues right in the editor according to their severity levels, it also provides commands for navigation between code issues.
If necessary, you can run code inspection for a specific project or the entire solution and check the list of issues found in the specified scope.
Also, you can enable the Solution-Wide Analysis that will detect all errors in your entire solution and extend the list of code inspections in the current file (e.g. it will find unused public members).
If needed, you can use code annotations to customize the way JetBrains Rider inspects your code.
Quick-fixes for code issues
JetBrains Rider helps you resolve most of the discovered code issues automatically. All you need is to press Alt+Enter when the caret is on a code issue highlighted in the editor and check the suggested quick-fixes.
JetBrains Rider also provides features that do not detect code issues automatically, but rather allow you to find potential problems yourself by deeper investigation of the code. For instance, you can study call chains and find origin and destinations of a specific value. For more information on these features, see the Code Exploration section.
You can use the following shortcuts for code analysis features:
For the full list of Rider keyboard shortcuts, see Keyboard Shortcuts Reference.