Tags: winfx
Tags: winfx
More on the death of WinFx (Part 3)
Posted Sunday February 4, 2007, 11:39 pm, Over one day old at Robert W. Anderson's Expert Texture
Read More on the death of WinFx (Part 3) (Links)
Reverse WinFX Petition . . .
Posted Thursday October 19, 2006, 11:06 pm, Over one day old at Robert W. Anderson's Expert Texture
The current versions of all implementations will be stuck at.NET 2.0; the next version will be forced to be called.NET 3.5 even though the?3? portion is absent on non-Win32 implementations. | | And why does that matter? | | 7.
Read Reverse WinFX Petition . . . (Links)
IE7 release date decoupled from Vista
Posted Thursday October 19, 2006, 11:06 pm, Over one day old at Robert W. Anderson's Expert Texture
Read IE7 release date decoupled from Vista (Links)
WinFx is dead
Posted Thursday October 19, 2006, 11:06 pm, Over one day old at Robert W. Anderson's Expert Texture
Customers / developers were not asking “what is WinFx?”, as much as they were asking, “where is the new managed Windows API, WinFx?”. | | But there is no managed Windows API. Not just the name, but the entire idea of a managed Windows API.
Read WinFx is dead (Links)
WinFx is Dead Part 2
Posted Thursday October 19, 2006, 11:06 pm, Over one day old at Robert W. Anderson's Expert Texture
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.
Read WinFx is Dead Part 2 (Links)
Renewing a request for .NET 3.0
Posted Monday August 14, 2006, 11:42 am, Over one day old at Robert W. Anderson's Expert Texture
Read Renewing a request for .NET 3.0 (Links)
WinFx becomes .NET 3.0
Posted Tuesday August 8, 2006, 2:58 am, Over one day old at Robert W. Anderson's Expert Texture
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. Is Microsoft saying that.NET 3.0 is the new Windows API?
Read WinFx becomes .NET 3.0 (Links)
.NET 3.0 (née WinFx) ? now with CLR 2.0!
Posted Tuesday August 8, 2006, 2:58 am, Over one day old at Robert W. Anderson's Expert Texture
So, no, there will not be a new CLR. | | Some people have complained that this introduces some confusion because the.NET product version number doesn’t match the CLR. This will save your ISVs some headache.| | | |Tags:.NET,.NET3.0, Microsoft, WinFx | |
Read .NET 3.0 (née WinFx) ? now with CLR 2.0! (Links)
A Vista plea to Microsoft
Posted Tuesday May 16, 2006, 6:11 am, Over one day old at Robert W. Anderson's Expert Texture
I can understand why Workflow Foundation may need to track the Office 2007 release, but do Communications Foundation (WCF) and Presentation Foundation (WPF) have to wait for Vista? Please do not wait for Vista’s release to make these components ready in final form.
Read A Vista plea to Microsoft (Links)