Alessandro Del Sole's Blog

/* A programming space about Microsoft® .NET® */
posts - 159, comments - 0, trackbacks - 0

My Links


Your host

This is me! This space is about Microsoft® .NET® and Microsoft® Visual Basic development. Enjoy! :-)

These postings are provided 'AS IS' for entertainment purposes only with absolutely no warranty expressed or implied and confer no rights.

Microsoft MVP

My MVP Profile

I'm a VB!

Watch my interview in Seattle

My new book on VB 2015!

Pre-order VB 2015 Unleashed Pre-order my new book "Visual Basic 2015 Unleashed". Click for more info!

My new book on LightSwitch!

Visual Studio LightSwitch Unleashed My book "Visual Studio LightSwitch Unleashed" is available. Click the cover!

Your visits

Follow me on Twitter!

CodePlex download Download my open-source projects from CodePlex!

Article Categories


Post Categories

.NET Framework


Help Authoring

Microsoft & MSDN

Setup & Deployment

Visual Basic 2005/2008/2010

Why you should use Visual Studio 2010 for Visual Basic 2005/2008 projects

In most cases, applications have quite long life. In other situations, today you might still need to create applications built upon .NET Framework 2.0 or 3.0 although we have .NET 3.5 SP 1. Similarly, when .NET 4.0 RTM will be available, in some circumstances you will still need building applications upon .NET 3.5 SP 1.

As it was for in Visual Studio 2008, Visual Studio 2010 (available in Release Candidate) also supports multi-targeting so it is able of creating applications targeting specific versions of the .NET Framework, starting from the 2.0.

The good news is that when you open old solutions or projects in Visual Studio 2010, the target Framework version will remain unchanged but you will be able of taking advantage of some new features in the IDE and in the language. About the IDE this is quite obvious: features such as the new WPF-based editor, zoom, advanced search and lots of new things are available.

The interesting thing is that you can also take advantage of new features in writing code, which are not available only for Visual Basic 2010. For instance, you can use the new Implicit Line Continuation feature, in order to avoid placing an underscore each time you need to split long lines of code. Also, you can write collection initializers. Just as an example, this code works in Visual Studio 2010 against a project built upon .NET 2.0 and written with Visual Basic 2005:

        Dim aList As New List(Of String) From {"One",



Another good reason to try Visual Studio 2010. Of course, take care: reverting the above code to older versions requires you to rewrite it according to the syntax rules available in the previous versions, other than requiring to revert the project/solution files manually.


Print | posted on lunedì 8 marzo 2010 00:55 | Filed Under [ Visual Studio 2010 Visual Basic ]


No comments posted yet.

Post Comment

Please add 4 and 2 and type the answer here:

Powered by:
Powered By Subtext Powered By ASP.NET