I have 6.1.1000.82 and this randomly happens sometimes even when not debugging. Have to close VS to bring back intellisense (at least that's my solution, there may be another)
scratch that. THIS time closing VS did not fix it. I had to go into resharper options and set it to VS intellisense, save, then set it back to resharper intellisense
This is not a known behavior. In order for us to have a chance of understanding what's going on, please start Visual Studio with these command line arguments: /ReSharper.LogFile "C:\resharper.log" /ReSharper.LogLevel Verbose Once you do that, please try reproducing this behavior, and if you succeed, provide the log to us for investigation. Thanks!
The next time this happens, try closing and re-opening the source file to see if intellisense starts working again. Most of the time this solves the problem.
I have 6.1.1000.82 and this randomly happens sometimes even when not debugging. Have to close VS to bring back intellisense (at least that's my solution, there may be another)
Hello
Could you please confirm that this still happens with the latest ReSharper 6.1? Thank you!
Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
I still use the version of 6.0,because version 6.1 has nothing in settings.
I have 6.1.1000.82 and this randomly happens sometimes even when not debugging. Have to close VS to bring back intellisense (at least that's my solution, there may be another)
scratch that. THIS time closing VS did not fix it. I had to go into resharper options and set it to VS intellisense, save, then set it back to resharper intellisense
Hello Collin,
This is not a known behavior.
In order for us to have a chance of understanding what's going on, please start Visual Studio with these command line arguments:
/ReSharper.LogFile "C:\resharper.log" /ReSharper.LogLevel Verbose
Once you do that, please try reproducing this behavior, and if you succeed, provide the log to us for investigation.
Thanks!
The next time this happens, try closing and re-opening the source file to
see if intellisense starts working again. Most of the time this solves the
problem.
"Collin Sauve" wrote in message
news:17711487.77411334087029528.JavaMail.devnet@confluence.jetbrains.net...
I have 6.1.1000.82 and this randomly happens sometimes even when not
debugging. Have to close VS to bring back intellisense (at least that's my
solution, there may be another)
---
Original message URL: http://devnet.jetbrains.net/message/5456743#5456743