Chapter 44. Upgrading with Visual Studio 2010
WHAT'S IN THIS CHAPTER?
Taking advantage of the new IDE when working on older projects
Updating projects to use the latest runtime and libraries
Each time a new version of Visual Studio is released, there is always a delay before developers start to use it. This is primarily due to the need to upgrade existing applications to a new version of the .NET Framework at the same time. For example, the migration from Visual Studio 2003 to Visual Studio 2005 required upgrading applications to version 2.0 of the .NET Framework. Since the introduction of multi-targeting in Visual Studio 2008, you have been able to upgrade to the latest IDE independently of moving to the .NET Framework version. This is particularly important if you still need to target older versions of Windows for which there is no support for the newer .NET Framework versions.
In this chapter, you see how easy it is to migrate existing .NET applications into Visual Studio 2010. This is done it two parts: upgrading to Visual Studio 2010 and then upgrading the .NET Framework version the application makes use of to 4.0.
UPGRADING FROM VISUAL STUDIO 2008
To begin with, let's start with a solution that contains a good mix of application types. Figure 44-1 shows a Visual Studio 2008 solution that contains Class Library, Unit Test, WCF Web Site, Web Application, Windows Application, Workflow Application, and WPF Application projects. The WCF Web Site, Web Application, Unit Test, and Workflow ...
Get Professional Visual Studio® 2010 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
