Hail .NET 3.0!

WinFx has been renamed to .NET 3.0. I think this is one of the smartest moves from the branding team in a long time. There was just too much confusion even within Developer Division. I’ve heard questions like do I have to install two separate frameworks? Why this new thing? Although I like the name WinFx better than .NET (If we had a time machine we could go back and rebrand .NET as WinFx 1.0, 1.1 and 2.0), I think it had to go.  

But I think they should have called this .NET 2.5. When LINQ, C# 3.0, the next VB (VB 9?) and CLR 3.0 come out, then it would truly be .NET 3.0.  Or rename it as C# 4.0 and call it .NET 4.0 when it releases.  But in all I’m happy that I don’t have to explain what WinFx is to my friends and can just point them to a redist and say install that and have ‘em all.

Comments (3)

  1. Deepa says:

    I don’t know about 3.0, maybe 2.1. My understanding is that WinFx is built on 2.0.

    What is "orcas" going to be 4.0?

  2. srivatsn says:

    2.1 would suggest a minor revision. And Avalon and Indigo and the rest are by no means a small revision. Again Orcas hopefully would be 4.0 and not 3.0 SP1 or some such mess like they did with XP.

  3. abhinaba says:

    I’m just happy they didn’t name it Microsoft Windows Framework 2006 .NET Professional Edition  🙂