
Microsoft · June 10, 2006
WinFX renamed to .NET Framework 3.0
In my opinion, this ROCKS. Though I have to admit the .NET moniker itself was almost destroyed when Microsoft started attaching it to everything. Remember .NET Server?
http://blogs.msdn.com/somasegar/archive/2006/06/09/624300.aspx
In my opinion, this ROCKS. Though I have to admit the .NET moniker itself was almost destroyed when Microsoft started attaching it to everything. Remember .NET Server?
Otherwise, I'm sure the .NET can last a few more years at least, before someone in marketing comes up with what they think is a better name. :)
I don't really care what it's name is. I just want my Framework to have everything I need. 2.0 when it was released roughly 6 months ago finally gained the things that were so desperately missing IMHO from 1.0. Serial Port communications stands out as the biggest hole, but there were others. But, needless to say, it's all in the past.
What matters now is that Microsoft is continuing the vision. I am thankful that the .NET moniker will at least see a few more versions. Since WinFX is .NET Framework 3.0, does that mean CLR 3.0 will just absorb WinFX (aka .NET Framework 3.0)? That's the only part that seems odd. You'd think it would be 2.5 and then in Visual Studio 2007 it would all be consolidated into .NET Framework 3.0.
Thanks to David Chappell for bringing it to my attention!