Troubleshooting and diagnostics
ReSharper ships a set of diagnostic commands that you run from the command palette. Open the command palette by pressing F1 and type ReSharper to see them.
Collect logs for a support request
Reproduce the problem so that it is recorded in the current session.
In the command palette, run ReSharper: Collect Logs.
Attach the resulting archive to your report in the issue tracker.
Capture backend traces
For performance problems or problems in the ReSharper backend, a plain log is often not enough. Traces record what the backend was doing in more detail.
Run ReSharper: Select Log Trace Scenarios and choose the scenario that matches your problem. To record a narrower set of data, run ReSharper: Select Custom Trace Categories instead and pick individual categories.
Run ReSharper: Capture Backend Traces, then reproduce the problem.
Run ReSharper: Disable Trace For All Categories when you are finished. Tracing slows the backend down, so leave it on only while you need it.
Reset caches
ReSharper keeps a cache of the symbols in your solution. If code inspections, navigation, or completion results look stale or inconsistent with the code on disk, the cache is the first thing to rule out.
Run ReSharper: Reset Caches in the command palette.
Reopen the solution and wait for the initial analysis to finish.
The backend fails to download
The first time you open a solution, ReSharper downloads a backend that matches your operating system and CPU architecture from download.jetbrains.com. If the download does not complete, check that your proxy or firewall allows access to that host.
When you cannot allow that access, install ReSharper from an offline VSIX package instead. The per-platform download links are listed in Install from VSIX. After the backend is in place, ReSharper works without a network connection.
Features conflict with other C# extensions
If code actions, completion items, or debugging behave unexpectedly, disable the Microsoft C# and C# Dev Kit extensions and reload the window, then check whether the problem persists.
Report a problem
Report bugs and feature requests in the ReSharper issue tracker. Include the logs collected above, your editor version, the ReSharper version, and your operating system and CPU architecture.