

This happens in ReSharper when you have two different versions of the same library in your solution.

I'm thinking of installing a new Windows :( Using some windows and registry repair tools I've done a lot of suggestions (of myself and others) I can't update any package (by "Packet Manager Console" or Manage NuGet Package) I can't install any package (by "Packet Manager Console" or Manage NuGet Package)

I can't add any reference to my projects (even inside new solutions and new projects) I realize that my Visual Studio also has bigger problems (More information on Stack Overflow) My solution has five projects > two loaded projects (main project + resource project) and three unloaded projects I've already uninstalled and installed ReSharper again. One month ago, I got these errors when I uninstalled Visual Studio 2012 RC and installed VS 2012 RTM. I tried ReSharper → Options → General → Clear Cache. The ReSharper “CANNOT RESOLVE SYMBOL” errors are everywhere, but my project build process is successfully, and it works correctly.Īdditional Note: If I disable ReSharper Code Analysis, my project will be Normal, but I want to use ReSharper code analysis. Here's hoping ReSharper v9.My Solution Build Status: Build Successfullyīut when I install ReSharper and ReSharper code analysis is enable, many keywords of my code are red with this error: However - at least in the case of the spelling mistake in a comment - the ReSharper Ctrl+Enter menu doesn't see anything worth fixing on that line and so that solution doesn't work.

ReSharper 9.1.2 merges its own quick-fixes and other contextually availableĪctions with Visual Studio’s own quick actions into its Alt+Enter menu In my experience even if there is no ReSharper issue on the line the Visual Studio quick action will not work for example, with Visual Studio Spell Checker extension finding a spelling mistake in a comment - ReSharper obviously has no problem with that line of code, the Quick Action is visible and works with the mouse, but the keyboard shortcut Ctrl+. Problem and provide a fix, you don’t have a way to choose Visual Quick actions: whenever both ReSharper and Visual Studio detect a The major issue with 9.1.1 is that it is blocking Visual Studio’s Unfortunately, on the ReSharper blog here for v9.1.2 they indicate that: I have the same issue with Visual Studio 2015 Community Edition and ReSharper v9.2.
