IntelliSense not working in ReSharper 6

I am running ReSharper 6.0 with Visual Studio 2008 and a ASP.NET project and IntelliSense is not working in my C# code behind files.  When I type in a period after an object, the drop down list with members does not appear.  If I hit Ctrl+Space it will come up.  If I uninstall ReSharper and reinstall it works for awhile but then eventually it stops working again.  I have also tried switching back and forth in the ReSharper Options -> Unse IntelliSense -> Resharper and Visual Studio but that doesn't help.  Any ideas?

2 comments

Hello John,

Could you please attach screenshots of ReSharper | Options | IntelliSense
| Completion Behavior and General tabs at the point when IntelliSense stops
working? Also, does it work fine in other types of projects (Class Library
for instance)? Thank you!

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

I am running ReSharper 6.0 with Visual Studio 2008 and a ASP.NET
project and IntelliSense is not working in my C# code behind files.
When I type in a period after an object, the drop down list with
members does not appear.  If I hit Ctrl+Space it will come up.  If I
uninstall ReSharper and reinstall it works for awhile but then
eventually it stops working again.  I have also tried switching back
and forth in the ReSharper Options -> Unse IntelliSense -> Resharper
and Visual Studio but that doesn't help.  Any ideas?

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



0

I opened a different ASP.NET project and IntelliSense was working.  So at that point I knew it was related to that solution.  So I closed the solution, deleted the _ReSharper.<project_name> folder and the <project_name>.6.0.ReSharper.user file, opened the solution again and let ReSharper process the assembilies and source files.  After that IntelliSense was working again.  Also I noticed that the warnings bar on the right side of the code pane was not present when IntelliSense was not working so something had to be wrong with the ReSharper cache.  

0

Please sign in to leave a comment.