SubscribeI’ve been using Visual Studio 2005 for over a year now, and in that time I’ve seen quite a few odd error messages come out of it. After a while I started collecting screenshots. So, that’s about all this post is going to be: a collection of random errors from I’ve seen while using VS2k5.
I get this when I try to close and the solution is still compiling. No problem, you’d think. Just cancel the build right? Nope, I get this if I build, cancel, then try to build again. Nothing appears to happen building the second time. I figure something is screwed up and try to restart, but I can’t. Every time I get this I had to kill Visual Studio with Task Manager. These days I just don’t use cancel.
Ah, corrupt resource files. The solution to this has been: 1) open resource file 2) delete stuff! One cause of this may be the vs designer serializing my classes into the resource file, but I think there is some other cause too. (here’s how to keep the designer from serializing your classes)
Random designer crash. The solution to this one is to close the document and reopen it. Sometimes it works, sometimes not.
I don’t have a clue what the cause of this was. The source file did indeed belong to the project, and I did a clean and rebuild just before getting this.
Here’s a favorite. Cannot write to the file. Fine, I’ll find what’s using it and kill it. According to Process Explorer, nothing but Visual Studio has the file open. I have to restart Visual Studio every time I get this one.
This just confuses me: a class cannot implement an interface method because it doesn’t exist, but it must implement the method. I’ve gotten this several times and each time went and checked that the return and parameter types are correct, everything is spelled correctly, etc. The fix: clean and rebuild.
No idea what happened here. Opened a file and the tab shows %2!
Not sure what it’s asking me. The debugger had already stopped on the line in the program where the exception was thrown. My answer didn’t seem to make any difference. With either yes or no, the exception continued.
Yay! the compiler crashed. If this happened once in a while it would be fine. However, this particular window comes up about 40 times in a row. Click Don’t Send or X and another shows up. The compiler is screwed until Visual Studio is restarted. This seems to have been fixed with the service pack.
I didn’t even know there was an undo manager…
Oh, an unexpected error. What, no more information? This didn’t seem to cause any problems. I clicked ok and kept working.
ok…
Anyway, just thought I’d share the random errors I see all the time. I was kind of wondering if anyone else out there gets nearly as many errors as I do. Many of these errors have occurred with vb.net. C# seems a bit more stable. The service pack seems to have helped a bit too.
Pingback: Visual Studio error messages..or...lack of useful information « Pale Musings
Nice one Dave. “Unexpected error” is of course one of my favorites.
Sometimes I get the Designer error, but not the others. Fortunately I use C#
Ah, to be able to work all the time in C#….’tis a dweam, within a dweam! C#, that sacrwed institution….
ahem…anyway…it must be nice Vladimer
At least I get to work in C# some of the time, more and more as time progresses.
Pingback: FCP.NoSabes! » Un blog que nos gana :(
Yes, I get most, if not all, of these errors. It’s so frustrating to be constantly having to restart VS.
I haven’t seen many of these in a while now. I don’t know if it’s because of the service pack or because I switched from mostly VB to mostly C#, but Visual Studio 2005 has been pretty good to me lately. I’ve been using 2008 for a few days and haven’t seen any odd errors yet.