I just installed build 216 for VS2005 (the first time I've installed a build
in a while, and first time on 2005)
During installation, when the console window came up, it looked like there
was some sort of exception in there... but it flashed by too briefly for me
to be sure or to get any other info about it. But that was something that
concerned me and thought you should know about it even if I can't give you
any further details.
After installation, I started up VS2005, and opened my usual working
solution (several projects, tons of files). Immediately I got the Resharper
exception dialog. I submitted it (successfully), and then dismissed it with
the "ignore further exceptions" check box. It then proceeded to chug away,
with the "More exceptions have occured" bar flashing in the bottom,
endlessly, several times a second, for MINUTES and MINUTES, while pegging
the CPU at around 60% usage.
Even as I write this, that exception bar is still flashing, indicating
they're happening over and over and over again.... presumably the same
I'm waiting to see if it ever starts actually analyzing any of my source
code, but for now, the only indication that Resharper is loaded is the
vertical scrollbar (after looking 'normal' for a while) finally moved over
and the erorr bar has been painted (but is blank, along with the red/green
status square... which says "Analysis will begin shortly").
While I can technically continue working, some other things aren't working
right and I don't know if it's because I have to wait for analysis to be
complete (and all those exceptions to stop... they're still going) or what.
But if I try to "Go To Class" with Ctrl+N and type in the name of a class
that is in my solution, in fact in the same project as the file I'm
currently viewing, and which is in fact already open in a tab, it still
takes me to the Object Browser, not to the class file. That's a problem...
even though all my "references" are DLL references, the fact that I'm in the
very same project and the file is already open in a tab means it should be
able to find the actual source I would think. Of course, it should work
even though I have DLL references and not Project references regardless...
is that support in yet?
I'm afraid this is as far as I'll be able to get with testing. I'm going to
have to uninstall and work resharperless until these exceptions are fixed.
And so far it's been about 20 minutes and there's no sign it's going to stop
throwing those exceptions or ever get around to analyzing my code, so I'm
just going to have to stop here, exit, and uninstall. Sorry! But 216 seems