VB.NET Refactoring Cut
Sam Gentile is not happy about the cutting of most of the refactoring functionality out of VS.NET 2005. I tend to stay on the C# side of the fence - just because that's the syntax I'm most familiar with and not because I think it's the one true way. So the VB.NET announcement doesn't really affect me. Regardless, the post got me thinking of the way Microsoft release Visual Studio in the .NET era. It seems to be a "big bang" approach after which you don't get any updates or service packs until the next major release. For example, where does "Check for Updates" get you with VS2003? There are certainly bugs in VS2003 that could have been fixed or minor functionality extensions that could have been added to keep developers happy in the drought between major releases.
So back to the VB.NET refactoring, why can't Microsoft have minor releases of Visual Studio 2005 that fixes faults that are found and adds the modules "that got left behind" like the full VB.NET Refactoring support.