Did you just take a dump on standard versioning practices?


Original source: http://blogs.msdn.com/b/endpoint/archive/2011/04/18/microsoft-net-framework-4-platform-update-1.aspx

Who was the genius that thought calling a 4.x update a “Platform Update 1” and referencing the knowledgebase would ever be a good idea? Does that person actually understand what he/she is doing?

WTF happened to calling things by Major/Minor version? As if the Client Profile wasn’t already a really stupid idea, now you come out with this crap.

Why are you messing people around like this? You realize some of us actually write software and deal with deployments?

15 thoughts on “Did you just take a dump on standard versioning practices?

  1. Stefan Daugaard Poulsen

    I can only agree, why not make it 4.1 or hell you can go for 4.0.1 or whatever.

    This is gonna break code for sure (we can always discuss the matter of bad code, but stuff will break from now on). I’m even to scared to even go look at writing a version checker for this…do we have to load an app and see if it’s possible to instantiate a statemachine? I know people already are struggling with the old 2->3->3.5 checking, due to the “updates”.

  2. Chad Myers

    It’s because they have such huge, painful process wrapped around releasing a new version (even minor) that they have to do tricks like this to get anything out. Basically the process is broken so the smart people find ways around the process and the whole thing ends up looking silly.

  3. Olaf Monien

    Actually I have another idea why they don’t just use x.y..z versions: There appears to be a company called ScrewThemAll Inc. that just recently acquired a patent that describes how to increment numbers and putting dots between them.

  4. Martin

    Did you have a look at the blog post? This is no normal update, which will NOT be pushed via Windows Update. This is only a special update for customers with special needs. It will be included in a future 4.1 or 4.5/5.0 or SP1 or whatever update.

    1. hhariri Post author

      And? How is that justifying anything? If anything it’s just making it even more complex. How is it that every other software can work with normal version numbers and not require all customers to apply it?

  5. victorwoo

    but Resharper 5.1 conflicts with .NET Framework 4 Platform Update 1

    Visual Studio 2010 with SP1, Resharper 5.1.3000.12

    After installed the VS10SP1-KB2495593.exe, and switch my WF ActivityLibrary project to target “.NET Framework 4 Platform Update 1(KB2478063), many of my code prompts the error:

    Module ‘mscorelib, Version, Culture=neutral, PublickKeyToken=b77a5c561934e089’ should be referenced

    If I suspending Resharper by “Tools | Options | Resharper | General | Suspend”, or by disabling by “Resharper | Options | Code Inspection | Settings | Enable code analysis”, the code displays normal.

    Microsoft .NET Framework 4 Platform Update 1 – Design-time Update for Visual Studio 2010 SP1 (KB2495593)


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s