ReSharper “Cannot resolve symbol” even when projec

Question

My Tools:

Visual Studio 2012 Ultimate + Update 1

ReSharper v7.1.25.234

My Solution Build Status: Build Successfully

But when I install ReSharper and ReSharper code analysis is enable, many keywords of my code are red with this error:

"Cannot resolve symbol XXX"

---

Another picture of my project >>

The ReSharper “CANNOT RESOLVE SYMBOL” errors are everywhere, but my project build process is successfully, and it works correctly.

Additional Note: If I disable ReSharper Code Analysis, my project will be Normal, but I want to use ReSharper code analysis.

---

I tried ReSharper → Options → General → Clear Cache. But I still have this problem!

---

• One month ago, I got these errors when I uninstalled Visual Studio 2012 RC and installed VS 2012 RTM.

• I've already uninstalled and installed ReSharper again. But I have this problem yet!

• My solution has five projects >> two loaded projects (main project + resource project) and three unloaded projects

---

I realize that my Visual Studio also has bigger problems (More information on Stack Overflow)

• I can't add any reference to my projects (even inside new solutions and new projects)

• I can't install any package (by "Packet Manager Console" or Manage NuGet Package)

• I can't update any package (by "Packet Manager Console" or Manage NuGet Package)

I've done a lot of suggestions (of myself and others)

• Re-resister some DLL files

• Using some windows and registry repair tools

• Remove ReSharper

• Repair Visual Studio

• and...

But I could not solve it.

I'm thinking of installing a new Windows :(

---

What is wrong, and how can I fix it?

Answer 1

Clear Resharper cache: Resharper -> Options -> General -> Clear Caches, close and reopen the solution. It worked in R# 9.0 Update 1

Answer 2

Above links of clearing the cache and/or suspending the ReSharper did not work for me. I just 'refreshed' the project, which was showing this problem, from the solution explorer and the problem goes away. Sadly, it keeps on recurring and only option it to keep on refreshing every time this problem recurs.

I have VS2012 with ReSharper 8.1 on Windows 8

Answer 3

For me for VS2015, I had to update Resharper to version 2016.2.2 to resolve the issue.

I had already tried (of which none worked for me):

• suspending / resuming
• suspending / clearing cach (using tools > options button) / resuming
• suspending / clearing cach (using Windows file system) / resuming
• moving cache to solution folder / restarting visual studio
• many other combinations of all or some of above

I hope that may help someone.

Answer 4

I ended up needing to request Resharper to clear its cache along with doing it manually through Windows File Explorer. This finally resolved the issue for me.

1. (As reported in many of the solutions here) RESHARPER > Options... > Environment > General > Clear Caches.
2. Close Visual Studio.
3. Go to this path in File Explorer for Resharper 10 in Visual Studio 2015: %localappdata%\JetBrains\Transient\ReSharperPlatformVs14
4. Delete all subfolders and their contents within that folder.
5. Restart Visual Studio, reload your Solution and wait for Resharper to initialize itself for the Solution.

Answer 5

I am using VS2015, R#10. None of the suggested solution worked for me. I deleted the contents of the bin folder of my solution and rebuild the entire solution, that seems to have resolved the issue. Before deleting the contents of the bin folder, I had tried suspending and resuming R#, doing clear cache from R# -> option -> general setting, and also manually deleting the contents from \AppData\Local\JetBrains\Transient\ReSharperPlatformVs12\v01\SolutionCaches.. Hope it helps someone.

Answer 6

I also saw similar problems reported in ReSharper which did not lead to compile/runtime errors.

These were mostly seen when using "{x:Type ...}" or "{x:Static ...}" markup, causing ReSharper to report "Cannot resolve symbol 'Type'" or "Cannot resolve symbol 'Static'" errors.

Additionally there were many errors like "Invalid markup extension type: expected type is '<type>', actual type is '...Extension'".

The problem resolved itself when I added a reference to the System.Xaml assembly.