jump to navigation

The relationship between .NET 2.0, .NET 3.0, VS2005, “Orcas”, ATLAS, C#3, VB9, LINQ and ADO.NET vnext October 3, 2006

Posted by Patricio in Coding, Orcas, Software Engineering, WCF, WF, WPF.
trackback

.NET 3.0 was a wierd marketing move because it sure as heck sounds like it’s a whole new version of .NET, but it’s really not.First a pretty picture:

The Framework

.NET 3.0 is.NET 2.0 plus the four new components. Those four core technologies are called the “.NET 3.0 Components“.

When you install .NET 3.0, it will put the .NET 2.0 framework and the .NET 3.0 components on your computer. If you already have .NET 2.0, then it will just add the 3.0 components. If you have Vista, it’s all there already since those .NET 3.0 tools are a core part of Vista as well. Looking in your folders, you will see the .NET 2.0 stuff where you are used to seeing it – in Microsoft.NET\Framework\V2.0.50727. There will also be a Microsoft.NET\Framework\V3.0 folder that has just the four .NET 3.0 components in it.

Nothing in .NET 2.0 is changing.

.NET 3.0 and Vista

The .NET 3.0 components are part of Vista. So programming with these components also allows you to leverage what is new and shiny about Vista.

Visual Studio “Orcas“

Like the relationship between .NET 2.0 and .NET 3.0, so goes the relationship between Visual Studio 2005 and “Orcas“. Orcas adds stuff on to what is already in VS2005: development tools that let you work with the .NET 3.0 stuff. For example, UI tools for building XAML (“Cider“), project templates and intellisense for the components, a UI tool for WCF as well. The last is not in the current CTP, by the way. So everything you already can do with VS2005, plus more.

ATLAS

First of all, ATLAS isn’t ATLAS any more it’s “ASP.NET AJAX“. AJAX is an extension to ASP.NET 2.0 that provides client side scripting libraries. It also has ton of controls that come with it. ATLAS, err, ASP.NET Ajax is not part of any of these other releases. It is currently autonomous and it works right along with VS2005 (though it’s still a CTP). Hopefully it will RTM by the end of the year. That will be v1.0. Then it will be wrapped into Orcas and get more goodies as well.

LINQ/C#3/VB9

These will be part of Visual Studio “Orcas“.

ADO.NET vNext

It’s very tempting to call this ADO.NET 3.0, but that makes it sound too integrated with .NET 3.0 which it is wholly unrelated to. ADO.NET vNext will be fully integrated with LINQ as well as adding some other awesome data access capabilities. But it is not coming out any time soon that I know of.

In addition to what I thought I already knew, I have spent a lot of time reading through “futures” documentation on the C# , VB9 and LINQ sites, on the ADO.NET site, on the Visual Studio site, on the .NET Framework site, the ASP.NET AJAX site, in forums and in blogs written by Microsofties.

by Julia Lerman

Advertisements

Comments»

1. lodine - February 3, 2007

lodine

news

2. buy phentermine - February 3, 2007

buy phentermine

news

3. Paul - July 6, 2007

Thank you, thank you, thank you for clearing this up. Why is this so hard to find out at MSDN? Again…thank you.

4. .NET versions, and: What is a GDR? at Fabian's Mix - June 28, 2016

[…] to call this “3.0″  was for it to sound better, and it really confused the quite many developers. But it got […]


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: