Friday, September 14, 2007

VS 2008 - A solution to long lived coupling between Visual Studio and .NET Framework

If you recall previous releases of .NET Framework which had a dedicated Visual Studio.NET linked to that particular .NET Framework version.

Lets see, all of them again:-

Microsoft .NET Framework | Visual Studio .NET
1- .NET 1.0 ---------------------- Visual Studio 2002
2- .NET 1.1 ---------------------- Visual Studio 2003
3- .NET 2.0 ---------------------- Visual Studio 2005
4. .NET 3.0 ---------------------- VS 2005 + VS 2005 extensions for .NET 3.0
5. .NET 3.5 ---------------------- Visual Studio 2008

This coupling in between has just put the entire Microsoft .NET aspirants to shift their focus to different IDEs and interfaces time to time for almost six years by now.

Visual Studio 2008(code named Orcas) is designed with a vision to support any .NET Framework version application in its single IDE, I.e, you don't need multiple copies of VS .NET to support different versions of .NET Framework (as shown above). Hence the Visual Studio 2008 reduces or removes the coupling between .NET Framework and Visual Studio .NET, and having just one copy of Visual Studio 2008 will cater the various .NET Framework versions.

The Visual Studio 2008 Projects Templates and how they support to .NET Framework versions is shown in the figure here:

You can see the vast range of Project Templates VS 2008 supports. Beisides on the top right corner of the figure shown just above, you can see while choosing a project template, it also allows you to choose your desired .NET Framework version from the dropdown list.

Hence, Visual Studio 2008 and its support for multiple .NET version support minimizes the maintenance and side-by-side issues which we all were facing due to the coupling betwenn VS.NET and their respective .NET Framework versions.

No comments:

Post a Comment