Mini-Microsoft, the anonymous Microsoft blogger and gadfly, collects a number of developer blog links to bug reports and some of the problems look rather nasty even for a first release. Be sure to read the comments on the posts as well. The net from Mini:
I might wander in early on Monday to meander through the crowds celebrating the big Visual Studio launch. But my heart is heavy that we shoveled what we could together and Won’t Fix-ed this release out the door. Microsoft has just opened a very big door to competition in the IDE space. Or at least towards people jealously holding onto VS 2003 and saying, “CLR 2.0? Screw that! The last time I tried to use generics my machine locked up!” Big freakin’ mistake. Microsoft should be ashamed.
Too alarmist? We’ll know shortly.
Update: More from Mini here:
In my opinion, what VS needs to do is say, in a manner that won’t dampen the launch party: Hey, this was a super-big innovative release but it looks like some bugs unfortunately shipped. Okay, we’re really going to ship a VS 2005 service pack. Here’s the Microsoft forum we’d appreciate you providing feedback to. Here’s a link that you can keep track of what’s going into the service pack. Furthermore, the service pack will ship on fill in a date no longer than six months out.
This is because the users are complaining that they’ve never, ever seen a patch or a service pack for VS and they expect they are going to be told to wait until the Orcas release. If that’s our plan, we should say so.
And frankly, for bugs that lock up the IDE and make the developer lose his work, that’s not what folks want to hear.