Recommended Posts

Just an update in that WinFX has been renamed to .NET Framework 3.0.

So by now it's:

Avalon -> WPF (Windows Presentation Framework)

Indigo -> WCF (Windows Communications Framework)

WinFX -> .NET Framework 3.0

InfoCard -> Windows CardSpace

This change of brand further emphasizes that WinFX never replaced Win32/64, but is simply a large set of .NET libraries that runs on top of it, now expanded for new features introduced with Windows Vista. In other news, Win32 has been upgraded for Vista as well, but the Win32 kernel functions has little else to do with WinFX / .NET 3.0 than the .NET API running on top of Win32.

I kind of understand the decision, since .NET is more established and WinFX after all expands on the libraries it offers. BUT... The confusing part is that the Common Language Runtime will still be 2.0 (since .NET Framework 2.0), and C# 3.0 and VB 9.0 with e.g integrated SQL queries is planned for .NET Framework 3.5 now. So .NET Framework 3.0 would basically expand on the API's, but not in other parts.

Another confusing part is that .NET 3.0 will be backported to XP and Server 2003, but .NET 2.0 was better backwards compatible than that. So I'm currently unsure if 3.0 will drop compatibility found in 2.0.

Since it doesn't update the core components and merely expand on libraries, I kind of agree with a person commenting on the blog post linked to above in that it should maybe have been called 2.5 to emphasize its 2.0 CLR reliance, and so 3.0 is reserved for the upcoming C# 3.0.

Edited by Jugalator
  • 2 months later...
  • 3 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.