Resharper 6 - cshtml / Razor Intellisense not working

I just upgraded to Resharper 6 and found a serious problem.  When I set Resharper's option under "Environment -> Intellisense -> General" to "Visual Studio", Intellisense stops functioning in cshtml files altogether.

How can I return to Visual Studio's Intellisense for ALL files, including cshtml?  I find the Resharper Intellisense replacement to be annoying, counter-intuitive, and incredibly buggy.

2 comments

Hello Tom,

I'm afraid I wasn't able to reproduce this behavior. Do I understand correctly
that built-in Visual Studio IntelliSense starts working as soon as you suspend
ReSharper under Tools | Options | ReSharper | General? Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I just upgraded to Resharper 6 and found a serious problem.  When I
set Resharper's option under "Environment -> Intellisense -> General"
to "Visual Studio", Intellisense stops functioning in cshtml files
altogether.

How can I return to Visual Studio's Intellisense for ALL files,
including cshtml?  I find the Resharper Intellisense replacement to be
annoying, counter-intuitive, and incredibly buggy.

---
Original message URL:
http://devnet.jetbrains.net/message/5308622#5308622



0

Another person on my team experienced the same issue as I did, also apparently due to installing Resharper 6.  However, after two days debugging the issue together and trying multiple machines, we finally found the culprit.  It is not related to Resharper.  It was coincidental that a change was made to a project file in source control at the same time that both of us upgraded to Resharper 6.  This change seemed innocent but breaks MVC support in Visual Studio, with or without Resharper installed.

The change that broke MVC switched the OutputPath from "bin" to "bin2\$(Configuration)".  The change was made because otherwise building both Debug and Release caused one configuration to overwrite the other one, and ASP.NET uses the "bin" path for its own purposes.  After experimentation we found that MVC breaks any time the OutputPath is more than one directory deep, and the top level directory is not "bin".  So "bin$(Configuration)" works, "bin\$(Configuration)" works, even "foo" works.  But "foo\bin" does not work because it is two levels deep and the top level is not "bin".

I apologize for assigning the blame for this issue to Resharper.  The cause was obscure and the timing was pure coincidence.  I am now using Resharper 6 again and hopefully will not experience any more strange issues!

0

Please sign in to leave a comment.