Expert Texture Home Contact me About Subscribe Digipede Connect on LinkedIn rwandering on Twitter rwandering on FriendFeed

rwandering.net

The blogged wandering of Robert W. Anderson

WinFx becomes .NET 3.0

S. Somasegar has announced that WinFx was confusing and so they have renamed it to .NET 3.0.

I’m indifferent or its good, wierd, or bad. What?

Indifferent: It is just a name.

Good: I like the idea that WinFx == .NET 3.0. It definitively shows how these technologies relate.

Wierd: I liked the name WinFx. As one of my Digipede presentations says, WinFx is was the new Windows API. Is Microsoft saying that .NET 3.0 is the new Windows API? That is hard to believe. Will WinFS end up being in .NET 3.0 or is that something else altogether?

Bad: Does this mean that the CLR is about to have a new version number? As Jesse Kaplan told me at PDC05, the biggest compatibility problem for .NET 2.0 was the version # (oh and installs that rely on the version # or some installation artifact to detect .NET). So is this going to happen again? So soon?

So, does it all matter in the end? I don’t know . . . it probably helps Microsoft focus its branding . . . that is a good thing.

    Trackback

2 Comments »

[…] I wrote about the WinFx name change on Friday, WinFx becomes .NET 3.0. […]

    Expert Texture » Blog Archive » Reverse WinFX Petition . . . wrote @ September 25th, 2006 at 9:06 am

[…] I have blogged on the change and have requested for decoupling .NET 3.0 from the release of Vista (here and here). This latter point is a bit different from the petition where it is being requested to go back and decouple WinFx from .NET. […]

Your comment

HTML-Tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>