I'm pretty happy with running VS 2008, especially since I've retrofitted my laptop with 4gig. But there are also a number of annoying bugs that occur rather frequently. This is especially frustrating because I pointed out a number of these during beta and they didn't get addressed. Let's see which ones you can identify with:
The missing View Source in the Web Editor
At times it appears that while you are editing an open document in the ASP.NET markup editor or the visual editor the View Source shortcut on the context menu is not there. It's inconsistent but quite annoying when it isn't. The behavior is also different in Web Application Projects and Web Projects. In Web Projects I never seem to see the View Source button. In WAP but menu option sometimes shows sometimes doesn't. There are other ways to navigate - you can use F7/Shift F7 to cycle through the various view modes of the designer,split, markup and source views although I find the keyboard shortcuts highly confusing as they change depending on which context you are in.
This Document is opened by another project with ASP.NET related files
Quite frequently I get this message in an warning dialog when opening files in ASP.NET projects. I'm very certain that the files are NOT open in another project. I do have other instances of VS.NET open usually but even after shutting them down and retrying - same deal. I get this error all the time now.
Open Folder in Windows Explorer bombs - always now
This handy feature worked for me at some point, but now all I get is:
This operation could not be completed. Unspecified error.
Thanks - that's very helpful. It's a little beyond me how a call to ShellExecute() can possibly be a problem <shrug>. But damn, I miss that feature already and I don't really want to install another add-in to get it.
Opening a Web Service or Handler in ASP.NET
During the VS 2008 beta there was some odd behavior where when you clicked on script mapped files like ASHX (handlers) or SVC (WCF Services) and the code editor would pop up the actual code instead of the small markup page - to actually get the markup page you had to use the shortcut menu. A little weird maybe but it's actually what I do most so this worked well. Looks like in RTM though that's gone. Not only that though with the View Source button missing the code behind file doesn't open except for having to hunt into APP_CODE manually. Minor annoyance, but still annoying.
IE Locking when starting to Debug Web Project
This is not a new problem - it's been around in Visual Studio 2003/2005, but it seems with VS 2008 it has gotten even worse. The issue is that when you start debugging a Web project it launches Internet Explorer and attaches the debugger for debugging. If IE isn't running no problem it all works fine. But if you launch a debug session (or Run a Web), keep it running and then later try to debug again IE will lock up. When it does Visual Studio will hang too as it now waits for Internet Explorer to respond . So now you have both IE and Visual Studio locked and IE won't shut down - it has to be killed. As soon as you do Visual Studio shuts down from debugging. This problem is likely due to issues with the COM Automation of IE and the way the debugger tries to attach to IE. And it's likely worse because the changes in script debugging in VS 2008 which by default enables script debugging. But there's gotta be some way to detect the state of the IE instance being attached BEFORE trying to attach and hanging it? Hey if necessary kill that IE instance and restart it for debugging - anything is better than hanging it!!!
This has gotten so bad I've switched to FireFox as my default debugging browser, but this isn't great either because VS will launch a new instance on the desktop each time and if you use FF you don't get script debugging through the project, which after all is one of the nice improvements in VS 2008. I'm pretty sure just about EVERYBODY debugging ASP.NET projects has hit this problem on a regular basis. This really needs to get fixed!
This reminds me of a funny incident at the MVP summit when Anders Hejlsberg was giving a LINQ demo using ASP.NET and ran into this bug every few minutes. Anders is a pretty calm guy usually, but you could tell he was gettin' pissed (and made some funny 'heads will roll' remarks - apparently an empty thread <g>) when launching and locking up IE. I feel the same way - this is a big time sink especially sometimes when IE will only kill with Task Manager (sometimes I can get it to kill by repeatedly clicking on the Close button but it depends how deeply locked it is).
All of these are annoyances more than anything, but they are enough of a problem to interrupt work flow significantly in bulk. Let's hope SP1 addresses these issues.