asp.net to 2.0

[JJ]

Right now, I have visual studio 2005 installed on my development server.
Currently the production asp.net application is running with 1.1 model. I
would like to convert my application to 2.0 in my development server and
deploy it to production (production server will have .net 2.0 installed but
not the visual studio 2005). How do I go about doing this?

Thanks

[David Wier]

In vs.net 2005, there is a conversion utility, if you open your 1.1 project
in vs.net 2005, it will convert it for you, and anything that wasn't
converted, you will get a message concerning that item - - if that list has
any items in it, you will need to address each item manually

depending on the size of your project, and how you coded certain items, this
could be an easy or a daunting task...Sometimes, if you have a long enough
list of these items, you might be better off starting from scratch...
:)

--
David Wier
MVP/ASPInsider
http://aspnet101.com
http://aspexpress.com
"JJ" <no****@nospam.comwrote in message
news:%2***************@TK2MSFTNGP04.phx.gbl...

Right now, I have visual studio 2005 installed on my development server.
Currently the production asp.net application is running with 1.1 model. I
would like to convert my application to 2.0 in my development server and
deploy it to production (production server will have .net 2.0 installed

but

not the visual studio 2005). How do I go about doing this?

Thanks

[Mark Rae]

"JJ" <no****@nospam.comwrote in message
news:%2***************@TK2MSFTNGP04.phx.gbl...

Right now, I have visual studio 2005 installed on my development server.
Currently the production asp.net application is running with 1.1 model. I
would like to convert my application to 2.0 in my development server and
deploy it to production (production server will have .net 2.0 installed
but not the visual studio 2005). How do I go about doing this?

1) Install SP1 for VS.NET 2005 if you haven't done so already.

2) Open up your v1.1 project in VS.NET 2005 and let the upgrade wizard
convert it for you.

3) Fix any errors which the upgrade wizard highlighted.

4) Test.

5) Install v2 of the .NET Framework on the server.

6) Deploy.

7) Return to the development project and look at ways you can improve it
using the new or updated functionality in ASP.NET 2

Some things to consider would be:

updating your DataGrids to GridViews

using System.Net.Mail instead of System.Web.Mail

using generics

MasterPages

XHTML compliance

[Cowboy \(Gregory A. Beamer\)]

There are 1.1 to 2.0 wizards in VS 2005. As David has mentioned, they are
hit or miss, depending on your own coding practices. In my sites, I have had
few problems converting, your mileage may vary.

There are few breaking forward changes from 1.1 to 2.0. Expect a little bit
of clean up when you migrate, however, as the wizards are not perfect and
you could well be a fringe condition. This is normal for any migration, of
course.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*********************************************
Think outside the box!
*********************************************
"JJ" <no****@nospam.comwrote in message
news:%2***************@TK2MSFTNGP04.phx.gbl...

Right now, I have visual studio 2005 installed on my development server.
Currently the production asp.net application is running with 1.1 model. I
would like to convert my application to 2.0 in my development server and
deploy it to production (production server will have .net 2.0 installed
but not the visual studio 2005). How do I go about doing this?

Thanks

[JJ]

I guess, I wan't clear enough.....the point was not to install visual studio
2005 in the production server and use development server to convert the
applicaition to 2.0 and deploy it to production.

I guess I am a little confused about the precompilation. Once I do the
procompilation at the development server, do I delete the virtual directory
in the production server and replace it with the folder created by the
precompilation?


"David Wier" <da********@noSpamhotmail.comwrote in message
news:uX**************@TK2MSFTNGP03.phx.gbl...

In vs.net 2005, there is a conversion utility, if you open your 1.1
project
in vs.net 2005, it will convert it for you, and anything that wasn't
converted, you will get a message concerning that item - - if that list
has
any items in it, you will need to address each item manually

depending on the size of your project, and how you coded certain items,
this
could be an easy or a daunting task...Sometimes, if you have a long enough
list of these items, you might be better off starting from scratch...
:)

--
David Wier
MVP/ASPInsider
http://aspnet101.com
http://aspexpress.com
"JJ" <no****@nospam.comwrote in message
news:%2***************@TK2MSFTNGP04.phx.gbl...

>Right now, I have visual studio 2005 installed on my development server.
Currently the production asp.net application is running with 1.1 model.
I
would like to convert my application to 2.0 in my development server and
deploy it to production (production server will have .net 2.0 installed

but

>not the visual studio 2005). How do I go about doing this?

Thanks

[JJ]

When you say deploy (step 6), are you just copying over the files to the
production server?
J

"Mark Rae" <ma**@markNOSPAMrae.comwrote in message
news:e7**************@TK2MSFTNGP05.phx.gbl...

"JJ" <no****@nospam.comwrote in message
news:%2***************@TK2MSFTNGP04.phx.gbl...

>Right now, I have visual studio 2005 installed on my development server.
Currently the production asp.net application is running with 1.1 model.
I would like to convert my application to 2.0 in my development server
and deploy it to production (production server will have .net 2.0
installed but not the visual studio 2005). How do I go about doing this?

1) Install SP1 for VS.NET 2005 if you haven't done so already.

2) Open up your v1.1 project in VS.NET 2005 and let the upgrade wizard
convert it for you.

3) Fix any errors which the upgrade wizard highlighted.

4) Test.

5) Install v2 of the .NET Framework on the server.

6) Deploy.

7) Return to the development project and look at ways you can improve it
using the new or updated functionality in ASP.NET 2

Some things to consider would be:

updating your DataGrids to GridViews

using System.Net.Mail instead of System.Web.Mail

using generics

MasterPages

XHTML compliance

[Mark Rae]

"JJ" <no****@nospam.comwrote in message
news:Ot**************@TK2MSFTNGP06.phx.gbl...

When you say deploy (step 6), are you just copying over the files to the
production server?

If you already have a virtual directory set up, and have configured it to
use v2 of the Framework, that's pretty much all you need to do.

You might like to have a look at this:
http://www.google.co.uk/search?sourc...oyment+Project

Superb add-in.