215 has a tendency to cause some rather annoying problems (the same as in
214 which made me revert to 213. still thinking about reverting again).
- sometimes, RS decides to use 100% of the CPU, apparently for the code
analysis (the little box up there stays with the clock icon). Needless to
say, it makes editing any code file rather impossible. I haven't detected
any reason for this to happen, but deleting the caches directory (and
restarting VS) seems to help.
- if I close VS while leaving a file open in the editor, then reload the
solution (I'm mostly launching VS via a .sln file), RS doesn't recognize
much of anything in this file. Not even fields. They're shown as unused on
their declarations and as unknown where they're used. Other files that were
left open but not active are not affected.
The easiest way I could find to fix this is to unload/reload the project.
Another way is, as above, to delete the caches directory.
Mmh, after some more tests (I'm writing this iteratively :), this only
seems to happen if VS is opened via the .sln file. If I first open VS then
load the solution file, it works.
- not specifically 215 related, but while I'm at it, I thought I'd mention
the quite persistent "VS has encountered a problem and needs to close" error
after it's been closed. I've become pretty much used to it (it's been
happening ever since I started using RS2.0, around build 209 if I remember
correctly), but it would be nice if somewhere along the line I didn't have
to uncheck 'restart VS' & click 'close' each time I close VS :)
Oh, and this problem still happens even if I load the solution after
opening VS :)
I'm not sure which of those are already known and which should be entered in
the tracker (especially the first one, since I haven't found a way to
reproduce it yet).