Why so slow with the Service Pack?

[CMM]

What's up with Microsoft's ludicrously slow response to the myriad of bugs
in VS2005 /.NET 2.0? After about 5 months of tinkering and prototyping, we
finally decided to shelve ALL projects scheduled for .NET 2.0.

We certainly didn't expect the fixes to take so long. Frankly, at this
point, (because so many of our applications are seriously aged and a clean
start is needed), we're looking to jump ship. Personally, I've had it with
Microsoft.

 

[Frans Bouma [C# MVP]]

What's up with Microsoft's ludicrously slow response to the myriad of
bugs in VS2005 /.NET 2.0? After about 5 months of tinkering and
prototyping, we finally decided to shelve ALL projects scheduled for
.NET 2.0.

We certainly didn't expect the fixes to take so long. Frankly, at
this point, (because so many of our applications are seriously aged
and a clean start is needed), we're looking to jump ship. Personally,
I've had it with Microsoft.

I'm with you that the service packs take too long (if they even
arrive), however if you're running into a bug, you could call PSS and
ask for the fixes. It is incredibly tedious and cumbersome, I fully
admit and I also don't understand why developers are threated like
secondclass customers but it's all you got.

FB

--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------