Friday, June 09, 2006
« CSLA .NET 2.0.1 available | Main | CSLA .NET 2.0.2 available »

According to this blog post by Soma, WinFX is now going to be named .NET 3.0.

Now on one hand this makes sense. There's no doubt that WinFX introduces major functionality to .NET. Windows Presentation Foundation is the effective successor to Windows Forms after all - how much more major can you get??

On the other hand, the new .NET 3.0 doesn't break any .NET 2.0 code, and yet it "includes" .NET 2.0. All .NET 3.0 does is add new stuff. Typically, when I think of a major version number changing, I expect that I'll have to retest everything and that much of my stuff might break or be affected. None of that is happening here.

Even changing from .NET 1.0 to 1.1 brought tons of headaches (if you used Remoting or Enterprise Services at least). And that was a point release. Yet here we have a major version change that doesn't change any existing bits.

I guess it just goes to show that there are no hard-and-fast rules in the software industry ;)

In any case, there's no doubt that Microsoft will reduce confusion overall by keeping everything under the .NET moniker, so I think this is a wise move.


Sunday, June 11, 2006 5:06:02 PM (Central Standard Time, UTC-06:00)
I think this is confusing because the CLR version is still 2.0
which means
.net 3.0 = asp.net 2.0 , ado.net 2.0 , clr 2.0 , wpf, wcf, wwf.

and No c# 3.0 or clr 3.0

so
.net 4.0 = clr 3.0 , c#3.0 ??

I think correct name should have been .net 2.1 or may be .net 2.5 but MS marketting would hate that:)



Vishal
Tuesday, June 13, 2006 3:17:42 PM (Central Standard Time, UTC-06:00)
It is a good move.

But now, what am I going to do with the domain www.winfxmasters.com?
Thursday, July 20, 2006 1:51:45 PM (Central Standard Time, UTC-06:00)
Okay... so how is one to implement the "Compact .NET 3.0 Framework" or "Mono 3.0"?
rei
Comments are closed.