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?
Try Visual Studio → menu Tools → Options → ReSharper, Suspend button and Resume again (no need to close the window). This works in my case.
VS -> Tools -> Options -> ReSharper Suspend button
Clear Contents of -> AppData\Local\JetBrains\ReSharper\v7.1\SolutionCaches
VS -> Tools -> Options -> ReSharper Resume button
This worked for me (VS2012u4, R# 7.1.3):
Resharper > Options > Environment: General > Clear Caches
Restart Visual Studio
Clear Resharper cache: Resharper -> Options -> General -> Clear Caches, close and reopen the solution. It worked in R# 9.0 Update 1
This happens in ReSharper when you have two different versions of the same library in your solution. For example project A references automapper version 1.1 and project B references automapper version 1.0.
Visual Studio will often compile and run as expected in the situation as it chooses one of the DLLs to bind to. However ReSharper gets massively confused. For me this should be a ReSharper error that it asks you to resolve rather than just going bonkers.
UPDATE:
I ran into this two days ago (a day after I made this post) by total coincidence and came across this link where they say that it is caused by a bug in the VS API. I tried everything that they recommended and was unable to resolve it even temporarily: I had Autofac 2.6.x that I'd downloaded from google.code and then swapped it over for the NuGet package version and it willfully refused to see the new reference no matter what I did.
They suggest installing the R# 8 EAP but for me it was less hassle to just downgrade to the old version of Autofac.
Not much in the way of help, but maybe useful.
This was happening to me with Visual Studio 2015 and ReSharper Ultimate 10.0.2. I tried pretty much all the solutions written prior to this answer (apart from any reinstallations) and nothing worked.
I got it working again with a variety of the above steps in a very specific order:
ReSharper → Options → Environment → General → Clear Caches
this must be done before suspending ReSharper as otherwise this option is unavailable
this clears out the files in C:\Users\YourUsername\AppData\Local\JetBrains\Transient\ReSharperPlatformVs14\v04 as mentioned in some other posts
Tools → Options → ReSharper Ultimate → Suspend
Close Visual Studio
this actually performs the ReSharper cache clear
Open Visual Studio
Open the solution
I waited for Visual Studio to detect there were no code issues in IntelliSense and may have performed a build at this point.
Tools → Options → ReSharper Ultimate → Resume
Hopefully after the last step you can breathe a sigh of relief that you don't have to reinstall anything, I certainly did!
It's usually happen by config file corrupt or wrong detect.
Just delete .vs folder, restart VS to reset config. It will work almost case
I had similar problems and cleared the caches found at:
AppData\Local\JetBrains\ReSharper\v7.1\SolutionCaches
Solved the problems for me
Running VS2012 u3
I had the same problem (VS 2017). In my case it was different versions of target framework - one assembly targeted 4.52, another 4.62 - after setting those to the same version in both assemblies it started working again.
As you see, the solution is what everyone has already mentioned - simply by Suspending ReSharper, then Clearing the Caches, and finally Resuming it. But, no one mentioned how to do it without closing/restarting Visual Studio.
Just follow these steps:
Getting ReSharper Cache Location
Manually by going to ReSharper Options > Environment > General > Store Solution Caches in (Combo Box) (marked 2 in the image). Selecting Custom Folder, then Copying the location of the Caches Folder from the text box shown (marked 3 in the image). Reverting the settings back. The 1 marked shows the ClearCache Button. It's usually wouldn't work so leave it.
Suspending ReSharper
You can do this by going to Tools > Options > ReSharper Or ReSharper Ultimate > Suspend Now (Button)
Clearing the Cache
Go to the location copied earlier in step 1 and delete everything in that folder. And yes, I do mean everything.
Resuming ReSharper
You can do this by again going to Tools > Options > ReSharper Or ReSharper Ultimate > Resume (Button)
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
I was just having the same issue with ReSharper 8.2 in Visual Studio 2013, and none of the usual solutions here of clearing caches, suspending ReSharper or re-installing ReSharper was working.
In my case I ended up solving it as follows... I looked at one of the symbols that it couldn't resolve and noted it was in System.Web.Http.dll. I then found that this was in the Microsoft.AspNet.WebApi.Core NuGet package. I used the package manager console to try and uninstall that package, except of course it told me that it couldn't due to other dependencies.
So I uninstalled each dependency up to and including Microsoft.AspNet.WebApi.Core, and then re-installed each package again in the reverse order. ReSharper picked everything up correctly as it was installed, and now seems fine.
I had the same issue and unloading and reloading problematic project helped me to clear out this issue for ReSharper. Hope this helps.
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.
(As reported in many of the solutions here) RESHARPER > Options... > Environment > General > Clear Caches.
Close Visual Studio.
Go to this path in File Explorer for Resharper 10 in Visual Studio 2015: %localappdata%\JetBrains\Transient\ReSharperPlatformVs14
Delete all subfolders and their contents within that folder.
Restart Visual Studio, reload your Solution and wait for Resharper to initialize itself for the Solution.
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.
Resharper -> Options
Caches -> Store solution caches in: (Change folder to another one).
Or try to manually clean up R# cache folder
I'm using 7.1, and this worked for me:
Uninstall resharper
go to %appdata% and remove JetBrains\Resharper and ..\Local\JetBrains\Resharper folders
re-install resharper
None of the cache cleanup worked for me. All of the symbols in any of our private NuGet repros just stopped being picked up with R# enabled, very frustrating.
I got this feedback from JetBrains support, which DID work, after toggling and restarting VS2019:
disable the following option - ReSharper | Options | Environment | General | Read solution model directly
I did everything above with no fix.
Then I did a step from another SO Q/A (don't remember which one) which was to set System.Web.Mvc to Copy Local true. Recompile my project and the errors went away.
When I set this assembly back to Copy Local false, the errors didn't return.
I my case, I tried all the suggestions above.
But, at some point I realized that the problem persists even if Resharper is suspended.
So, I looked for similar problem in VS itself and found the solution in the comments for the accepted answer in this SO post.
I'm listing my steps for brevity.
VS -> Tools -> Options -> ReSharper Suspend button
Build solution. Notice all references still unresolved
Clean the solution
Restart VS
Build the solution without Resharper. Notice all references resolved
VS -> Tools -> Options -> ReSharper Resume button
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.
I was having the same issue in my Visual Studio 2015 with Resharper Ultimate and tried the solutions as suggested above, but none worked for me.
Then upgrading Resharper to latest release solved my issue.
What helped in my case after several of the suggestions above didn't:
Removed one project reference (of one of the libraries where ReSharper claimed not to be able to find it even though it was correctly referenced).
Use ReSharper’s "Resolve" on one of its usages to add the reference again.
After that, it worked fine, even though none of the project files were actually modified in the process.
I have the same problem.Clean Resharper cache and Suspend Resharper not worked for me.I just close visual studio, uninstall Resharper,and then install Resharper,the problem was gone.
I was referencing a NetStandard2.0 project that didn't get recognized by R#.
I cleared the caches but that did not help me.
Downloading the latest version and updating R# did work for me.
This is the version I'm now running:
JetBrains ReSharper Ultimate 2017.3.2 Build 111.0.20180201.63358
ReSharper 2017.3.20180201.111630
Just download R# and it will recognize already installed versions. Updating to the latest version is really easy.
When I disabled ReSharper, Visual Studio was also giving the same error, even though the project built successfully. What I did to resolve the issue was:
Remove the project from the solution.
Right-click the solution, Add Existing Project, select the project file and add it again.
After performing these steps, the syntax errors went away in Visual Studio, and after I enabled ReSharper again, it also had no errors.
I also had this problem. All previous solutions did not help for me or helped for a very short time.
In my case, the problem was that I connected the .Net Framework 4.7.2 project to a project that has version 4.5.2. After I updated both projects to version 4.7.2, the problem was resolved.
I think that to solve the problem you need to have the same version of the projects. Or connect a smaller version to a larger one, but not vice versa, as was the case in my case.
In Rider 2020.3 I just did a Build -> Clean, and then it worked.
For me, I think my solution just got caught in a weird state when I was changing which branch of my local Git repo I was on. Simply switching to the previous branch I was on before the problem started, telling VS to reload all the files, then switching back to the desired branch and reloading again fixed it.
We saw this problem as well, specific to files which were shared by multiple projects. There is a combo box in the upper left corner of the editor window that lets you switch project context for the file (and hence the references that impact symbol resolution).
Resharper makes it easy to accidentally open the wrong "version" of a shared file by its "go to file or symbol" commands.
Switching context back to the project I use in the solution was all I needed to do to fix this issue.
Related
I am getting this incredibly annoying warning for every C# file in my ASP.NET Core project when I debug it after hitting F5:
Because this error appears only during runtime (not during build), I can't even suppress it using the "Suppress warnings" box in the project properties. I've tried putting 1003 and ENC1003 in there and it still appears, cluttering up my warnings window. Does anyone know why this thing is appearing and how I can get rid of it?
UPDATE: It doesn't fix the fundamental problem which is that the warning is generated in the first place, but I've found a way to suppress it. Create a GlobalSuppressions.cs file at the project root, and add the line:
[assembly: System.Diagnostics.CodeAnalysis.SuppressMessage(null, "ENC1003")]
Related Github issue: https://github.com/aspnet/AspNetCore/issues/13284
Try to get the Lastest Version of your Visual Studio and try again, If Persist, Install Visual Studio 2019 v16.4 Preview 2.
Also Check out the following content>> https://developercommunity.visualstudio.com/content/problem/601258/edits-were-made-to-the-code-which-cannot-be-applie.html. You can also track this same issue on ASP.NET Github: https://github.com/aspnet/AspNetCore/issues/13284. We already have a fix for it, which will be available on Visual Studio 16.4 Preview 2
I was facing the same problem in my Visual Studio 2019, and therefore I had to update VS to the latest version and I was good to go.
Hope helps someone :) :)
You can go to build options and select the option to build solution (build->build solution), this should solve the problem and you will able to continue your project in solution mode.
I had this problem also in Visual Studio 2022 (17.0.5) running API projects. Restarting Visual Studio helps.
In the past, while debugging UAP apps, if I edit the code while the app is running it will let me know that it needs to recompile the whole application. (Usually when adding some sort of static variable or removing a function etc... Tht in and of itself is not a bug.
The bug is that when I STOP debugging, the error remains until I restart the IDE.
I would argue that suppressing the warning is a horrible idea - It means that you have no way of knowing if the code changes you made during debug were implemented.
Instead, try restarting the IDE and doing a clean and build. I don't remember what I do to make the error go away anymore, as I have not experiences this bug in at least 8 months.
I have a solution in Visual Studio 2017 where projects reference other projects in the solution; when I open the solution and I open a project the references to code defined in other projects seems not resolved (is like the other projects had not yet been loaded) I must click every single projects, expand it and then the reference are all resolved. Is there a work around to avoid this?
UPDATE: I have Lightweight Solution enabled for the single solution
and Resharper installed.
To be clear the solution builds but visual studio show me in red references to code in other projects and i get errors in the error windows even if the building succeed
UPDATE 2 As suggested by Pankaj Kapare if I disable the Lightweight modality for the solution the problem disappear but still persist if I enable Lightweight again
You may have turned "Lightweight Solution load" option on. You can disable it using following steps:
Go to Tools > Option > Projects and Solutions > General settings page.
Uncheck "Lighweight solution load for all solutions" if its checked.
Reopen Visual Studio.
For those who (like me) applied the solution by #Pankaj Kapare and still had the same problem:
Go to Tools > Options > Projects and Solutions > General
Notice the message May be overridden for individual solutions
Make sure Always show solution is ticked
click OK
Open Solution Explorer with Ctrl+Alt+L
click the solution
hit F4 to open Properties
Make sure Lightweight load is set to Disabled or Default
I resolved this issue by deleting the csproj.user file.
I am having an issue with Specflow remaining disabled in Visual Studio extensions.
When I start VS I get an error SpecflowPackagePackage didn't load correctly.
I tried to uninstall and reinstall specflow but it seems weird. When I uninstall it says uninstall successful and asks to restart VS. When I restart Specflow is still there but disabled.
Using Visual Studio 2015, Update 3, 64bit. Windows 10. Specflow Version 2017.1.6
I had a similar problem. However, it's happened for me on Visual Studio 2017, then I went to Control Panel/Programs and updated the Visual Studio 2017. It's worked for me.
I don't know what caused the problem. But the way I fixed was:
NOTE This might delete all plugins.
delete everything in below folders (with VS closed)
C:\Users\<username>\AppData\Local\Microsoft\VisualStudio\14.0
C:\Users\<username>\AppData\Roaming\Microsoft\VisualStudio\14.0
And reinstall the plugins along with specflow.
If someone can post a better answer please feel free to.
Go to the top menu -> Tools -> Extensions and Updates. On left navigation menu, be sure Installed -> All is selected. Find Specflow extension in the list and click it. Click Enable button and restart VS.
Upgrading Visual Studio to the latest version fixed the issue for me.
NOTE: I believe the accepted answer works because the SpecFlow extension gets removed. If you don't need SpecFlow then uninstalling it from Tools->Extensions and Updates menu also works.
Under tools --> Options (settings)--> extension and updates --> Change your Extension and Update settings , check the Load per user extension checkbox
I have installed Visual Studio 2015 Professional Edition, and my computer specs are Intel i7-3770 CPU 3.40 GHz, 8 GB RAM, and Windows 7 Enterprise 64-bit.
I want to upgrade my project to .NET 4.6 which is written in Visual studio 2005 .NET 2.0, but I have a serious problem about speed. After I open my project (huge project) in Visual Studio 2015 it is going crazy. Building, debugging, opening menus are too slow. Sometimes I got "not responding" message. Is it about Windows 7 or can you give me any advice about my speed problem?
You can try to apply the following steps:
Go to menu Tools → Options → Source Control and set Current source control … to None
Go to menu Tools → Options → Environment (or Accounts) → Synchronized Settings and remove this option by unchecking the checkbox.
Clean the contents in the following cache folders (do not delete these folders, instead delete their contents only) and restart Visual Studio:
Clean the content in WebSiteCache folder (can be found in C:\Users%USERNAME%\AppData\Local\Microsoft\WebSiteCache)
Clean the content in Temporary ASP.NET Files folder (can be found in C:\Users%USERNAME%\AppData\Local\Temp\Temporary ASP.NET Files)
Note: If you have Hardware Acceleration enabled or if you use the default Visual experience settings in Microsoft Visual Studio 2015 or Visual Studio 2013, you might experience intermittent performance issues, product crashes, or rendering issues. In order to work around these issues, go to menu Tools → Options → Environment → General and apply the following settings:
For more information, visit You experience performance issues, product crashes, or rendering issues in Visual Studio 2015 and Visual Studio 2013.
If the problem is related to debugging, try the workaround on Visual Studio debugging/loading very slow.
This site contains some useful tips on how to improve the Visual Studio performance, disabling features for large solutions. For example:
Go to Tools -> Options -> Text Editor -> C# -> Advanced and uncheck Enable full solution analysis
Go to Tools -> Options -> XAML Designer -> General and uncheck Enable XAML Designer (requires restart of Visual Studio)
Go to Tools -> Options -> Text Editor -> All Languages and uncheck Enable CodeLens
Go to Tools -> Options -> Debugging -> General and disable Enable Diagnostic Tools while debugging
I have a large project and have experienced these kinds of slow downs too. I've improved the performance to an acceptable level by changing the scope of the Error List window to Current Document.
I also get improvements by changing from Build + IntelliSense to Build Only. But because I find the IntelliSense useful, I compromised to keeping Build + IntelliSense and scoping to Current Document.
I have found that removing the ".vs" folder from your solution folder greatly increases editor speed if it becomes slow over time. It is a hidden folder in the root directory of your solution. I would recommend saving a backup of it just in case you need to revert. As far as I know, it holds user specific settings for the solution such as the .suo file as detailed here. You can try just removing the .suo file too. These folders/files will be regenerated by VS the next time you open and close that solution.
The Windows Defender Antimalware can cause Visual Studio to lag. As mentioned by Nostradamus in this answer:
Go to Update & Security -> Settings -> Windows Defender. Open the Defender and in the Settings selection, choose Exclusions and add the "devenv.exe' process.
Another thing I did was update ReSharper and every addon to the latest update.
I also noted that several processes called Microsoft Compatibility Telemetry, CompatTelRunner.exe was using a lot of CPU when I used Visual Studio. I disabled "Feedback and diagnostics" by following this guide.
It worked for me!
Is it possible that you were trying to do different operations on solution at the same time? In my situation, the problem appeared because I was trying to open solution, while there was a process from TFS, which was trying to get latest version. Some kind of lock happened.
Safest way I thought of was to restart the system, delete .suo file and it worked for me.
What else: check if your visual studio version is 64bit on 64bit system, I have uninstalled some team foundation power tools and it screwed with my VS, it produced the same problems
Make sure you're not working on a solution that's on a network drive.
Seems like such an obvious thing, but I missed it, and VS gives you precisely no hints as to the problem, it's just lots of "Not Responding...".
For me the culprit was Resharper cache, simply clear Resharper cache and it works fine
I suggest the quickest and easier performance enhancement (for C#) is to replace VS 2015/2017 with VS2013.
C# is largely unchanged between versions. It just takes twice as long to use 2015/2017 and I am sure I am not the only one to waste time using later (better)compilers only to have to revert.
I do not think it is unreasonable to expect to use a compiler straight out of the box. You can with 2013.
Microsoft MUST ensure VS2019 is at least as fast as 2013 (for C#)
I accidentally mashed a couple of keys together at the same time and now delete and backspace no longer work inside code blocks on aspx pages. ReSharper functionality such as autocomplete (Alt+Enter) is still working just fine. I've tried
devenv /resetuserdata
but with no luck. With ReSharper disabled everything works just fine but I much prefer coding with it turned on.
I should mention I'm using ReSharper 4.5
I have tried upgrading to the latest version (4.5.1288.2 at time of writing)
I have tried uninstalling and reinstalling ReSharper
I have uninstalled ReSharper, reset all user settings in Visual Studio, deleted all files in
C:\Documents and Settings\user\Application Data\JetBrains
and reinstalled ReSharper. Still no joy.
Update: Problem only occurs on pages that are not included in the open solution (a developer forgot to include them) but are present in the solution's folder structure. Obviously I have solved my problem by including the necessary files but now I'm going to see if I can recreate this on another machine.
And you checked that the keys aren't bound to a command somewhere? All bindings can be found in Tools -> Options -> Keyboard. I did the same thing once, and some of my buttons started acting wierd. I fixed it by tracking down the keybinding and deleting it in the preference menu.