Solution-wide analysis

Enable solution-wide analysis

Solution-wide analysis can take some time for the initial processing of the solution and therefore, it is disabled by default. You should switch it on explicitly for every new solution you open.

Alternatively, you can right-click the circle indicator in the right corner of the status bar and use the context menu to toggle solution-wide analysis. If solution-wide analysis is off, just double-click the gray circle.

tip

In large solutions, solution-wide analysis may result in some performance degradation, especially at the initial analysis phase. However, there are several ways to improve the performance of solution-wide analysis.

After you have switched on solution-wide analysis, several changes are made:

• The status-bar indicator displays the progress of the analysis. After the analysis completes, the indicator turns green (if no errors/warnings were found), orange (if warnings in solution-wide analysis are enabled and if there are warnings in the solution), or red (if errors were discovered):

  

• A small area to the left of the circle indicator is allocated to show the number of solution files that contain errors/warning, if any. You can click this area to go to next error/warning in the solution.

• Solution-wide code inspections for non-private members become available both in the design-time code inspection and when you inspect code in a specific scope.

  tip

  You can view the list of ReSharper's configurable code inspections on the Code Inspection | Inspection Severity page of ReSharper options (Alt+R, O). Solution-wide inspections can be recognized by the Non-private accessibility tag.

• Names and semantics of the navigation commands in the ReSharper | Inspect menu change. Specifically, Next Error/Warning changes to Next Error/Warning in Solution and Previous Error/Warning becomes Previous Error/Warning in Solution.

Monitor warnings in solution

If you monitor warnings in the solution, the analysis becomes more resource-intensive and can affect performance on large solutions. Therefore, you can explicitly enable or disable monitoring of warnings.

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.

Study the list of errors/warnings

While solution-wide analysis is enabled, you can use the status bar indicator to monitor errors/warnings in solution, but you can also get a detailed report on all errors/warnings in your solution in the Errors/Warnings in Solution window.

tip

You can share found issues by copying them to the clipboard or exporting to a file.

Even without opening this window, you can still easily navigate through errors in your solution with Alt+Shift+PageDown/Alt+Shift+PageUp ( ReSharper | Inspect | Next Error/Warning/ ReSharper | Inspect | Previous Error/Warning) , or just by clicking the number of errors/warnings to the left of the status bar indicator.

tip

As an alternative to monitoring errors/warnings in solution, you can find all issues in your solution or smaller scope and view them in the Inspection Results window.

Performance of solution-wide analysis

The main calculations of solution-wide analysis are performed when you first enable it. Depending on the size of your solution, these calculations may take from several seconds up to dozens of minutes. You will still be able to keep working, but some performance degradation is possible.

Once these global time-consuming calculations are finished, only necessary incremental analysis will be performed according to modifications.

When enabled, solution-wide analysis might also extensively use memory. If you notice that your system resources suffer too much, you can do one of the following:

• Configure the list of files, file masks, and folders to skip when performing code analysis.

• Edit the list of files and regions containing generated code to simplify analysis of such code.

• Pause the analysis when you do not need it and resume it only when you need it again.

• Exclude warnings from the analysis.

If you turn solution-wide analysis off and then decide to turn it on again, ReSharper will have to repeat some of the initial calculations, which may be time-consuming. To avoid this, you can pause and resume solution-wide analysis instead.

Ignore errors/warnings in solution

At some stage of your solution development, you may have too many errors/warnings known to you. ReSharper allows you to flexibly ignore some errors or error-containing files and not include them into solution-wide analysis results.

Such items will be hidden from the error list in the Errors/Warnings in Solution window and they will not affect the state of the status bar indicator. When necessary, you can stop ignoring these items to display them.