My first BIG Visual Studio 2003 crash – Update

The last couple of years I’ve had small Visual Studio crashes, where Visual Studio stopped and asked me if I wanted to restart and reopen the current project. These crashes never meant a loss of work. Today I had the first BIG VS2K3 crash and this time it did cost me. A lot…

I’m wondering why VS stopped responding completely. The network here at our client isn’t that fast this morning, but I can not imagine this being the problem. I installed ReSharper a couple of days ago, but I would think a lot of people use this. So I don’t think that’s it either, because I couldn’t find anything on their site (only for (much) older versions). Then what was it? A hardware failure? A rare VS bug / feature? Too many heavy apps opened? I don’t know. But I do know I will be CTRL-S’ing more often…

Update:
It does seem to be a bug. The problem occured again, at exactly the same place it did half an hour ago. There’s one method in my Workflow which (ReSharper) Intellisense does not like too much. And when I complete the method call without Intellisense I don’t have Intellisense at all for the workflow object. When I reboot Visual Studio after saving the method that caused this problem, all’s well and I can continue my work…. Strange stuff.

• dotnet
• Visual Studio