VS.NET 2003 to VS.NET 2008 conversion

29 May 2009 2:10 PM

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.

29 May 2009 2:33 PM

Tom Shelton

On 2009-05-29, Amritha.Da***@gmail.com <Amritha.Da***@gmail.com> wrote:

> 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.
>

If your using VS2003, then that is not framework 2.0 - it is 1.1. If it was
VS2005, then you would be 2.0.

Show quoteHide quote

> 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.
>
>

You do not have to make use of any new features - though once converted, you
might find some of the new features useful going forward...

For the most part, your conversion is probably going to be open the old
project in the new ide and recompile. You might find a couple of small
issues, maybe a few compiler warnings about obsolete classes/methods - but I
wouldn't count on to many major headaches.

That said, make sure you follow good source control practices, in case you
need to go back again.

--
Tom Shelton

29 May 2009 2:45 PM

Cor Ligthert[MVP]

To add something,

Be aware that you probably will think that some controls are gone.
They are still there but not direct visible standard anymore in that
toolbox, you can add them simply to the toolbox by right clicking and
selecting again.

Cor

Show quoteHide quote

"Tom Shelton" <tom_shel***@comcastXXXXXXX.net> wrote in message
news:ujJXupG4JHA.240@TK2MSFTNGP06.phx.gbl...
> On 2009-05-29, Amritha.Da***@gmail.com <Amritha.Da***@gmail.com> wrote:
>> 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.
>>
>
> If your using VS2003, then that is not framework 2.0 - it is 1.1. If it
> was
> VS2005, then you would be 2.0.
>
>> 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.
>>
>>
>
> You do not have to make use of any new features - though once converted,
> you
> might find some of the new features useful going forward...
>
> For the most part, your conversion is probably going to be open the old
> project in the new ide and recompile. You might find a couple of small
> issues, maybe a few compiler warnings about obsolete classes/methods - but
> I
> wouldn't count on to many major headaches.
>
> That said, make sure you follow good source control practices, in case you
> need to go back again.
>
> --
> Tom Shelton

29 May 2009 2:52 PM

Tom Shelton

On 2009-05-29, Cor Ligthert[MVP] <Notmyfirstn***@planet.nl> wrote:

> To add something,
>
> Be aware that you probably will think that some controls are gone.
> They are still there but not direct visible standard anymore in that
> toolbox, you can add them simply to the toolbox by right clicking and
> selecting again.
>

Yes... Good point, Cor.

--
Tom Shelton

29 May 2009 3:32 PM

sloan

Dot NOT multipost:

http://groups.google.com/group/microsoft.public.dotnet.general/browse_thread/thread/df04970e8ae41dbf#

http://groups.google.com/group/microsoft.public.dotnet.languages.vb/browse_thread/thread/b2325b4870834f18#

<Amritha.Da***@gmail.com> wrote in message
Show quoteHide quote

news:202491c7-26e7-4501-a5e6-cc246eecfb9e@s31g2000vbp.googlegroups.com...
> 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.
>
>