Freigeben über


.NET Framework 3.0: Clearing the Confusion

This past Friday, Soma announced .NET Framework 3.0. Customers are already asking things like "is C# 3.0 going to be in this? What about LINQ? How about WinFS?"  Sorry, stuff like C# 3.0 (if that ends up being its name, I have no idea) and features like LINQ are not shipping with .NET Framework 3.0.

Let's attempt to clear this up.

.NET Framework 2.0 + WCF + WPF + WF + WCS = .NET Framework 3.0

.NET Framework 3.0 uses the same C# and same features that were released in October 2005 with .NET 2.0, formerly code-named "Whidbey").  We didn't change the framework, we just added a couple new things to it.  The block diagram for .NET Framework 2.0 looks like this:

.NET Framework 2.0

The .NET Framework 2.0 is what comes with the .NET Framework 2.0 Runtime, the .NET Framework 2.0 SDK, Visual Studio 2005 Standard, Visual Studio 2005 Professional, Visual Web Developer 2005 Express Edition, Visual Basic 2005 Express Edition, etc. This is what you are using today with ClickOnce, Membership providers, the new GridView control, the new databinding stuff, all the goodness that you are currently using.

.NET Framework 3.0 is an additive release to .NET Framework 2.0, adding WCF, WPF, WCS, and WF capabilities.  Think of these as the additions formerly known as WinFX.  We just added a few things to the same goodness that you are using today in .NET 2.0.  To help clear up some of the confusion, this is what .NET Framework 3.0 looks like:

.NET Framework 3.0

Again, note that .NET Framework 3.0 is an additive release to .NET Framework 2.0.  With .NET Framework 3.0, the languages still use the 2.0 compilers, and leverage the 2.0.50727 Framework. 

[Update: Thanks Christophe Lauer for the suggestion to highlight the additions formerly known as WinFX]

Comments

  • Anonymous
    June 11, 2006
    The next version of Microsoft development framework that ships with Vista and has a down-level support...

  • Anonymous
    June 11, 2006
    I'm a little slow on this one due to having a life on the weekend (well, a life without work anyway),...

  • Anonymous
    June 11, 2006
    PingBack from http://thejoshblog.wordpress.com/2006/06/12/joshback/

  • Anonymous
    June 11, 2006
    Kirk Allen Evans has the best explanation so far of what comprises the .NET Framework 3.0. It can be...

  • Anonymous
    June 12, 2006
    PingBack from http://shafraz.wordpress.com/2006/06/12/net-framework-v30/

  • Anonymous
    June 12, 2006
    By now I'm sure most of you have seen the announcement that the WinFX framework has been rebranded as...

  • Anonymous
    June 12, 2006
    As most of you know already, Soma Somasegar, announced last week that the WinFx has been rechristned...

  • Anonymous
    June 12, 2006
    The CodeRyder blog quoted my posting on .NET Framework 3.0:

    Kirk Allen Evans clearly stated that this...

  • Anonymous
    June 12, 2006
    Late last week, Soma posted the news that we're harmonising the naming for .NET and WinFX under one umbrella:...

  • Anonymous
    June 12, 2006
    Microsoft a officiellement annoncé le changement de nom de WinFX (l'ensemble des API fournies avec Vista),...

  • Anonymous
    June 12, 2006
    Microsoft a officiellement annoncé le changement de nom de WinFX (l'ensemble des API fournies avec Vista),...

  • Anonymous
    June 14, 2006
    AT LAX, waiting on a plane to Atlanta, I bought a book, "The World Is Flat: A Brief History of the Twenty-first...

  • Anonymous
    June 19, 2006
    Find it a good clarification on the confusion of WinFX and .NET Framework 3.0.

  • Anonymous
    June 19, 2006
    Microsoft has just announced the change of the name of WinFX to .NET 3.0:
    http://blogs.msdn.com/somasegar/archive/2006/06/09/624300.aspx...

  • Anonymous
    June 20, 2006
    No matter how do you try to clear, it will always be confusing... .NET 3.0 = .NET 2.0 + XYZ...?

    Why don't just call the thing .NET 2.2!

  • Anonymous
    June 20, 2006
    No matter how do you try to clear, it will always be confusing... .NET 3.0 = .NET 2.0 + XYZ...?

    Why don't just call the thing .NET 2.2!

  • Anonymous
    June 20, 2006
    No matter how do you try to clear, it will always be confusing... .NET 3.0 = .NET 2.0 + XYZ...?

    Why don't just call the thing .NET 2.2!

  • Anonymous
    July 12, 2006
    James has just posted these links. Keeping it here for self reference [I]Microsoft.NET 3.0 MSDN Site

  • Anonymous
    July 12, 2006
    What with the announcement of WinFX being renamed to .Net 3.0, there has been some confusion as to exactly...

  • Anonymous
    July 19, 2006
    Si vous ne savez pas à quoi correspond la dénomination ".NET Framework 3.0", vous devriez jeter un oeil...

  • Anonymous
    July 19, 2006
    PingBack from http://microsoft.wagalulu.com/2006/07/19/vous-avez-djentendu-parler-du-net-framework-30-non-mais-si-bien-sur/

  • Anonymous
    August 27, 2006
    About .Net 3.0

  • Anonymous
    January 30, 2007
    PingBack from http://www.buunguyen.net/blog/?p=13

  • Anonymous
    February 09, 2007
    Asa cum spunea si Todi , numele de marketing al noului framework va fi .NET Framework 3.0. Detalii in