I'm having major problems with Resharper ocne a refactor, auto correct or anything else fails for whatever raeson (mostly because a file that needs to be checked out is locked by another user and/or results in merge failures).
You always seem to get an exception.
Some are very nasty and probably need a check/safeguard call before trying to actually do the changes.
I open a file which has unknown references (due to a component swap (new version) at the fielsystem level). The fiel that now has errors is checked out by another user. I go to the error and hit alt-enter, enter to select the presented solution. This results in 2 exceptions and after that Resharper no longer sees the error. Rebuilding will cause Visual studio to highlight the error, but Resharper won't find it till the whole file needs reparsing. This leads me to think that a rollback isn't executed where needed.
If you paste a block of code (a couple of properties+backers for example) in a file checked out by someone else you get a huge number of exceptions. I'm not sure it's fr every character, token or line pasted, but it's really annoying. Any change attempt like this should first check if the file can be checked out and stop if it can't be.
Refactoring a property that is used by almost every class in the project fails now and then (see rename error post a couple of hours back). Not only because a file cannot be checked out, but sometimes arbitrary. If you hit Build solution then to check if anything was broken by the failed attempt all incorrect (changes will be saved) causing mayhem if you had other changes open in the editor. A Message alerting that there are stil unsaved changes in files open in the editor before starting the refactor (with an option to save these changes) would be nice in these cases.
If you continue working after any of these issues, the IDE often locks up completely going into a spin and takign all available memory. I recently go a new computer, but 1Gb of memory if fille din no time this way ;). If you manually stop the add-in you usually get an exeption (caught by VS, not Resharper) and cannot restart the addin (or open the add-in manager for that matter as that results in a nullpointer exception).
I really hope all this get's fixed in 210 as its driving me mad }:-> .