ReSharper 2026.3 Help

General

ReSharper options: Environment | General

This page of ReSharper options summarizes general settings of the ReSharper environment.

User interface

Application icons theme

Chooses the icons used in the ReSharper interface. Keep Automatic selection to match the current theme, or select Color, Gray, Light Theme, Gray, Dark Theme, Fluent Design, Light Theme, or Fluent Design, Dark Theme. The preview below the list shows the selected icon set.

Source code symbols theme

This list lets you switch between different sets of code symbol icons. You can leave the default option of automatic selection or choose an icon set that will be most comfortable for you for the selected Visual Studio theme. You can preview the selected icons below the list and see them when using Go to features or Explore type hierarchy.

Use compact spacing in tree views

Reduces spacing between items in ReSharper tree views so that more items fit on the screen. This option is disabled by default.

Show managed memory usage in status bar

If this checkbox is selected, the amount of managed memory used by the whole process is shown in the rightmost position of the status bar. This value indicates not only the amount of managed memory used by ReSharper but also the amount of managed memory used by other third-party plug-ins and Visual Studio itself.

Localization

Interface language

Use this list to change the user interface language to Chinese, Japanese, or Korean.

Region and culture

Region

The region preference affects how ReSharper work by adapting to regional specifications. For example, it can change the URLs used to access various services, switch to a region-specific LLM provider for AI Assistant, or route traffic through a local proxy. Such adjustments optimize ReSharper performance and ensure that its functionality complies with local regulations.

Caches

Store solution caches in

ReSharper caches a lot of its temporary data. For example, results of code analysis. If you do not share the solution, you can choose solution folder. If you share your solution using a VCS, it is better to choose the system temp folder so that ReSharper gets them out of the solution folder and therefore out of the way of your VCS. It is recommended to choose a custom folder. The problem with the 'User local settings folder' %LOCALAPPDATA% is that Visual Studio's directory watcher could be triggered when ReSharper writes to this folder, which happens very often.

You need to reopen your solution for changing caches location to take effect.

Custom folder location (prefer SSD over HDD)

Specifies the root folder for caches when Store solution caches in is set to Custom folder. Choose a folder on an SSD for faster cache access. Reopen the solution to apply the new location.

Clear caches and restart ReSharper

Marks the current solution caches and shared ReSharper caches for deletion, then restarts ReSharper. This button requires an open solution.

Normally, you do not need to clear solution cache, but some events (for example, sudden power off or an upgrade that skips several versions) may corrupt the cache, and that is when you need to use this button. Signals of corrupted cache may be a lot of unresolved code or absence of ReSharper inspections in some files.

If the Options dialog contains modified settings, ReSharper postpones the restart. Apply or discard those changes, or click Discard modified settings and restart ReSharper. After the restart, ReSharper rebuilds its caches.

Restart diagnostics

Send restart diagnostics

Controls whether ReSharper sends diagnostic data collected during its restart to JetBrains.

  • Ask every time: ask before sending diagnostics. This is the default.

  • Always send: send diagnostics without asking.

  • Never send: do not collect or send restart diagnostics.

Solution Model

Read solution model directly from project/solution files

For most of its features (including navigation, code analysis, refactorings, and code completion) , ReSharper builds and maintains a model of the current solution. The model is cached and then used to instantly access any item in the solution structure.

By default, ReSharper reads project and solution files independently of Visual Studio. This method is preferred because:

  • it does not use Visual Studio COM API and therefore does not block the UI thread,

  • it renders a more reliable model for projects targeting multiple frameworks.

However, it has some minor side effects:

  • ReSharper needs projects and solution files to be up to date. Therefore, in case the files were edited but not saved, it will save them automatically.

  • Theoretically, there could be extremely rare coincidences when you can have a Cannot access file error during the build because ReSharper has temporarily locked a project file. In this case, you can just start the build once again.

If some of the above is a problem, clear this checkbox to make ReSharper read solution structure via Visual Studio COM API, which can be a bit slower.

Alternatively, you can configure this behavior per project: right-click the project in the Solution Explorer, select Edit project item properties, then choose Read project model from project file | True or False.

MSBuild Access

Use MSBuild to obtain project references and generated files

This selector allows you to define whether to call MSBuild to analyze project references in web projects or projects that have NuGet references. Results of this analysis are used by code inspection and other related features. It helps you choose the appropriate balance between performance and the precision of the analysis.

  • Do not call MSBuild: ReSharper avoids calling MSBuild, which ensures the fastest performance but might result in incomplete code analysis for projects with complex build configurations.

    Recommended for simple projects without conditional references or code generation.

  • Call automatically on NuGet changes or if project contains conditional references: ReSharper automatically decides when to call MSBuild based on the project characteristics. This option offers a balanced trade-off between performance and accuracy.

    Suitable for most development scenarios.

  • Obtain data from MSBuild after each compilation: ReSharper calls MSBuild after each compilation to retrieve the most up-to-date project information. This guarantees the highest accuracy in code analysis since it always has the latest project references and generated files, but may result in performance overhead due to frequent MSBuild invocations.

    Recommended for complex projects involving extensive code generation, conditional compilation, or dynamic references.

09 November 2026