Conversion from .NET 2.0 to 3.5; VS 2003 to VS 2008

  • Thread starter Thread starter Amritha.Datta
  • Start date Start date
A

Amritha.Datta

Hi -,

We are planning to convert our current project which was developed
in .NET framework 2.0 and VS 2003 to .NET framework 3.5 adn VS 2008.

I am not much familiar with the advantages being converting the
project to .NET 3.5. Only thing that I know is we will get MS support
if the project is converted.

Current project developed on ASP.NET and VB.NET is code behind. We
have many business layer components, Datalayer components and Windows
services developed in VB.NET

Presentation layer (asp.net website) calls business layer components,
business layer components calls data layer components, and datalayer
calls stored procedures and insert/retrieve data from oracle database.

Windows services are folder watch services. As soon as they see a new
file dropped into the folders, they trigger the start process and
calls busines, data layer components for various activities.

We have used data grids extensively in web site.

I want to know your openion on how can we convert this project using
VS 2008 framework 3.5. Do we need to use any of these new features
such as WCF, WPF, Windows Work Flow, Windows Cardspcae, LINQ and Data
awareness?

Plese respond with your comments

Thanks.
 
Hi,

Visual Studio 2008 can target .NET Framework 2.0 you don't even need to
use 3.x features.

On the other hand .NET Framework 3.0 and 3.5 are just extensions to 2.0,
there is no such thing as a 3.x runtime or a whole 3.x class library,
just some extra 3.x assemblies. If you have .NET Framework 2.0 SP2 you
have all the updates to the 2.0 components that 3.x contains.

As a result you can use your existing 2.0 assemblies and you simply will
benefint new features of the development environment and optionally get
the opportunity to use the new features of .NET Framwork 3.5.

Kornél
 
Back
Top