How to make ReSharper re-evaluate its assembly ref

问题:

I am creating a Prism Project Template, and the template works great. But after I create a project with the template some of the files look like this:

Despite appearances, everything is just fine.

If I do a Rebuild All I see that the solution builds with no errors:

But the rebuild all does not get rid of the "errors" that are showing in the editor window. (Note that the actual error window does not show any errors.)

I can clean, rebuild, close and open files, and it will not fix the highlighting.

However, if I close the solution and re-open it, all is well:

My Question:

Ideally there would be a way for my template or my IWizard to tell ReSharper to reload the references for the highlighting.

I know I can turn ReSharper off and then on again and that will fix it, but I would rather not do that.

Is there a ReSharper command that just refreshes this stuff?

回答1:

Except for reinstalling, the only way to successfully clear the caches is to delete the files manually from your AppData directory.

Delete the solution folder that's giving you grief in the following locations:

• %LOCALAPPDATA%\JetBrains\ReSharper\v7.1\SolutionCaches\
  
• %LOCALAPPDATA%\JetBrains\Transient\ReSharperPlatformVsXX\vXX\SolutionCaches\ for newer versions.

Note that the version numbers in the paths may be different depending on the ReSharper version that is installed.

The XX in vXX and VsXX represents any number, because there might be multiple folders where the solution cache is stored.

回答2:

Try unloading and then reloading the project.

To unload the project, right-click the project in the solution explorer, and select Unload Project. Then, right-click the project again and select Reload Project.

The issue continues to occur occasionally with the latest versions of ReSharper, but the fix seems to work for every version.

回答3:

You could try clearing the ReSharper cache via menu ReSharper → Options → Environment/General → button Clear Caches.

回答4:

This worked for me. There is no need to reload projects. You can do this from within Visual Studio.

1. Clear the ReSharper cache via ReSharper, Options, General, click 'Clear Caches'.

   

   

2. ReSharper, Windows, select 'Solution Errors'. This will launch the Solution Errors window. At the top of this window, click the button to 'Reanalyze Files With Errors/Warnings'.

   

   

回答5:

Open ReSharper - Options - Environment - General, scroll down to Msbuild access and select Obtain data from msbuild after each compilation.

This worked for me, using ReSharper 10.0.1 with ReSharper Build.

回答6:

Go to ReSharper → Windows → Solution Errors Window, and you will get an overview of the errors in your solution. There, you can click the button Reanalyze Files With Errors.

If you want, you can assign a shortcut to this. Go to Tools → Options → Keyboard, and search for "Reanalyze". You can assign a keyboard shortcut to either 'ReSharper_ErrorsView_ReanalyzeAllFiles' or 'ReSharper_ErrorsView_ReanalyzeFilesWithErrors'.

回答7:

I have a similar issue with nuget packages and I found a most weird workaround: select the reference in project reference list and press 'F4'. Somehow properties window appearance causes resharper to reevaluate available references...

回答8:

I am not certain this is the same root cause, but I discovered that, within the ReSharper options, "Use MsBuild" was checked and I got all sorts of erroneous errors reported. Try checking "ReSharper->Options->General" and see what state the "Use MsBuild" check is in.

回答9:

Go to ReSharper → Options → General and click Clear Caches. (I have 8.2, so if you're on a different version it may be elsewhere.)

You'll then need to re-open your solution, and ReSharper will re-analyse everything.

回答10:

The only thing that helped me is: Unistall and than Install Resharper again (Repair didn't work)

Visual Studio 2010 SP1, ReSharper 7.1.3000.2254

回答11:

This is a strange issue, and is still alive and well in version 8.2.3 (build 8.2.3000.5176).

What seems to work for me on a consistent basis is to do a solution rebuild.

In VS 2013: Build -> Rebuild Solution

回答12:

If the solutions above don't work you can try resetting the project output type. This seems to fix the issue on VS2015 Update 1 with ReSharper 10.1

回答13:

Run the following code in a command prompt. Then solve the ReSharper issue...

del /q/f/s %TEMP%\*

回答14:

For me none of the above worked. I had to install the new version of Resharper which supports NET Core 2.0.