Visual Studio 2015 Broken Razor Intellisense

Question

After installing and then repairing my VS2015 instance I still cannot get intellisense (server side) to work in my MVC views. I get alerted by message promp

Answer 1

You don't need to reset everything just remove all files from %LocalAppData%\Microsoft\VisualStudio\14.0\ComponentModelCache and restart VS, it'll be fine.

Answer 2

I met the same problem, but the cause was different from the other answers.

An update of Visual Studio (I suspect TypeScript update on September 2015) uninstalled the Web Developer Tools component of Visual Studio 2015. That causes IntelliSense not to work.

I installed Web Developer Tools in the installer options again AND deleted ComponentModelCache after the installation. That worked for me.

Answer 3

This fixed it for me right away.

In Visual Studio:

Click Tools->Options->Text Editor->All Languages->General Uncheck "Auto list members" Uncheck "Parameter information" Check "Auto list members" (yes, the one you just unchecked) Check "Parameter information" (again, the one you just unchecked) Click OK

Answer 4

To add my 2 cents. None of the previous solutions worked for me, then I found this link:

http://www.c-sharpcorner.com/blogs/how-to-resolve-intellisense-issue-in-visual-studio1

In particular this one

Solution 4:

Next, reset the Settings from the following location.

Tools->Import and Export settings->Reset all settings.

From there I choose Visual C#

Answer 5

I solved this problem by resetting the user data

devenv.exe /resetuserdata

and remove the ".vs" folder in my project.

---

WARNING: this will reset all your user settings. Essentially, it is like resetting to factory defaults. You will lose any custom keyboard shortcuts, extensions you've installed etc.

Answer 6

FWIW, I had this problem with VS 2015 Enterprise on two different machines. On one machine, resetting user data made the problem go away (for a while). On the other machine, I had to totally uninstall and reinstall VS, and the problem went away for a while. On both machines, the problem came back after I installed an extension (once when installing Web Essentials, once when installing Git Diff Margin).

I burned an MSDN tech support case, and the answer was... Yeah, it's a bug, MS knows about it, and they're working on it.

Not a particularly actionable answer, but an answer nonetheless...

EDIT: And on the subject of working around the problem, I've encountered the problem a few more times since I posted this "answer". Most recently, I installed an update to NuGet Package Manager, and when VS restarted it started having this problem. I ran devenv.exe /resetuserdata, but that didn't help; it was still broken. So I tried again (ran devenv.exe /resetuserdata) and, bada bing bada boom, the problem went away (for now). The moral seems to be something along the lines of "if at first you don't succeed..."