Visual Studio 2012 - Intellisense sometimes disapp

Question

My colleagues and I are using VS2012 for some weeks now. Sometimes after working several hours the intellisense is broken. After closing all open tabs it works again.

Are there more people out there having the same problem? It can't be an extension problem because I have the same problem at home. Maybe there is a workaround for this?

Answer 1

I had an issue with razor Intellisense not working at all in one of my projects. None of the fixes above worked for me. I was finally able to resolve the issue by changing the webpages version in the web config to 2.0.0.0 instead of 3.0.0.0 shown below:

<appSettings>
   <add key="webpages:Version" value="2.0.0.0" />
   ...
</appSettings>

I hope this helps someone else.

Answer 2

Steps to follow:

1. Go to Tools Menu
2. Click on "Import and Export Settings"
3. Select "Reset all settings". Click Next
4. Back up your Settings. Click Next
5. Select your environment settings(e.g. Visual C# Development Settings). Click Finish.

No need to restart the Visual Studio.

Answer 3

I was having a similar issue in Visual Studio 2013, I just cleaned the solution and then deleted 4: Close Visual Studio 2013 and delete this folder: %AppData%\Microsoft\VisualStudio\12.0 and it solved the problem.

Answer 4

I had some bad xaml code. It wasn't giving an error when compiling, but it was still preventing the intelliSense from working properly within the xaml file.

I removed the following code to fix the issue: Binding="{Binding ReturnCode & Info}"

the '&' being the problem

Answer 5

The problem is with the .vcproj files.

You will find if you switch to release mode from debug mode, build, then try intellisense it often works.

Close Visual Studio. If you search for the .vcproj files in your project, edit them and search for the first two instances of AdditionalIncludeDirectories. The value for this should look something like "..\,....\" rather than "../..".

Reopen your project, let the Intellisense finish building, then it should be fixed.

Answer 6

I faced this problems multiple times and I still face it too.

The solution which worked for me was to reduce the length of the path where the solution is placed. I placed the solution closer to C drive (c:/code/your_project.sln) and it just solved the intellisense problem This always solves the problem.