After I posted WinFx is Dead, I’ve gotten two kinds of comments:
Didn’t you hear that WinFx has been renamed .NET 3.0? What rock have you been hiding under?
Well, yes, I have heard that — my point wasn’t that the name WinFx is dead, it is that the concept of WinFx is dead.
Really, Microsoft has killed the managed Windows API?
What, am I psychic?
I have no idea if Microsoft has killed the managed Windows API. It appears to me that they have. The stated reason for the name change was to clear up confusion in the marketplace. The common belief seems to be that this confusion was that developers didn’t understand how WinFx related to .NET. I believe that the actual confusion was that developers didn’t understand how WinFx (as composed of WCF, WPF, WF, etc.) had anything to do with a managed Windows API.
I am guessing that this name change away from WinFx is indicates that the managed Windows API is dead. John goes further in comment on this post (full comment here):
. . . Microsoft continues to vacilate on this issue. I hear Microsoft execs stand up and proclaim that everything is .NET. Then I see product teams create products without the slightest nod to .NET, using a patchwork of unmanaged code and interfaces dating back to the (early) COM days.
So, Microsoft: you may think that the name change cleared up some confusion. Maybe it did. But as a Microsoft ISV, Gold certified partner, developer, I’ll tell you that I’m confused about how .NET actually fits into the overall product plans.