What!? .NET 2.0 SP1 in 2007? Unacceptable!

Brad Abrams blogs:

George asks about SP1 of the .NET Framework 2.0... Again the details have not been 100% worked out, so don’t take this as an official statement, but I expect SP1 of the .NET Framework 2.0 to be at the same time as Orcas .NET Framework ships.

Well, I don't know about you, but I personally heard from mr. Somasegar that .NET 2.0 would get a service pack in 2006 and not at the end of 2006, if I might add. Orcas is slated for release in 2007, and not early 2007. This means we'll have to wait for at least one whole year before a service pack for .NET 2.0 is released.

Unacceptable. Why on earth is Microsoft so stubborn that they sit on their patches for years instead of releasing them to the public?

10 Comments

  • Agreed. Fully. Looks like someone at MS is a real idiot on that.

    Especialyl the hotfix situation (yes, PLEASE PLEASE PLESAE have the customer call PSS) is ridiculous.

  • If we take a look at the following page, "Visual Studio 2003 Service Pack 1 ships Q2, 2006" and "Visual Studio 2005 Service Pack 1 ships Q3, 2006": http://msdn.microsoft.com/vstudio/support/servicing

    Ok, this is for Visual Studio and not the .NET Framework, but I would expect the service packs to come in pairs.
    If these dates are not maintained, I agree that this is unacceptable! Come on, the service pack for VS 2003 more than three years later, and the service pack for VS 2005 when the next version is released?!

  • What about a service pack for Visual Studio 2005? That would also be welcome as there are also some hotfixes people would really like, as well as some improvements to the general sluggishness of the IDE and other stuff for example Asp.Net precompilation that's extremely slow.

  • I agree with you, waiting 2007 for a Service Pack is a bit too much.

  • Not disagreeing with anyone here and while I am sure many appreciate this, I feel I have to clarify it for those that don't:
    A Visual Studio service pack and a .NET Framewok Service Pack are two distinct things, shipped at two distinct times.

    Now that the fact is clarified, my *opinion* is that that is a good thing: I wouldn't want to wait for a SP for one just because the SP for the other is not ready. Decoupling of release dates by the teams, brings us the goodness when it is ready.

  • Initially the first SP for Visual Studio 2005 should have even be released before SP1 for Visual Studio .NET 2003 due to the high number of issues with Visual Studio 2005. Releasing the SP1 for Visual Studio 2005 makes more sense since Microsoft wants to release a SP or Service Release normally two years after the release date of a product and normally 4 years after that release a major new thing. This means that the first real "new" Visual Studio should be released Q4 2009 (?)

  • Someone definitely needs to create a list of VS hotfixes. That would at least allow us to service pack our own vs installations...

  • "Someone definitely needs to create a list of VS hotfixes. That would at least allow us to service pack our own vs installations... "
    That will be very hard as you have to call PSS to get the hotfix in most cases. I've been bitten by desigenr problems, and the KB even indicates that there is a bugfix, but I have to call PSS for that. Why can't they just make the bugfix downloadable, even if I had to install it at my own risk ?

  • Thats absurd, I've been waiting with baited breath for this SP ever since 2005 came out. Don't get me wrong, I'm happy to be on VS2005 and some of the new features bring a smile to my face, but I can't help but think how rushed the release was in the end, and since the release they have (hopefully) made a lot of fixes that should be out NOW!! And don't ge me started on VS2005 performance....

    Grrrr

    Matt

  • You mean the SP for .NET 3.0 which is really .NET 2.0 but it's not really .NET 2.0 ?

    :)

    I can just see it now: "it says .NET 2.0, but I have .NET 3.0 - and yet because .NET 3.0 is really .NET 2.0 you should apply this 'service pack'.

Comments have been disabled for this content.