ASP.Net conversion projects 1.1 to 2.0 CLR

[SenthilVel]

Hi All

During the migration of my web project from 1.1 to 2.0 we found a web site
to have a download for a MS patch for the conversion of the web projects to
happen.

The link is :
http://msdn.microsoft.com/asp.net/re...p/default.aspx

http://www.microsoft.com/downloads/d...displaylang=en

In the local developer machines , when we want to do this conversion i
downloaded both the above and made the conversion.

My Question is :

1. In my machine where i install my web application must i also have this
downloads there inorder to have ASP.Net 2.0 to opn my converted aspx pages?

2.Or once i check in my converted aspx project, files , i can just package
and installl in any machine where CLR2.0 is present ?

what must be dont at the install level ?

Thanks
Senthil

[Cowboy \(Gregory A. Beamer\)]

Once you have properly converted to 2.0, you should not need anything else.
The exception is the web applications projects (originally posted and still
available at www.asp.net). This uses a more 1.x like model for compiling the
web applications with CodeBehind rather than partial classes. Without it,
you cannot compile using the older coding model.

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

*************************************************
Think outside of the box!
*************************************************
"SenthilVel" <se******************@misyshealthcare.comwrote in message
news:up****************@TK2MSFTNGP02.phx.gbl...

Hi All

During the migration of my web project from 1.1 to 2.0 we found a web site
to have a download for a MS patch for the conversion of the web projects
to happen.

The link is :
http://msdn.microsoft.com/asp.net/re...p/default.aspx

http://www.microsoft.com/downloads/d...displaylang=en

In the local developer machines , when we want to do this conversion i
downloaded both the above and made the conversion.

My Question is :

1. In my machine where i install my web application must i also have this
downloads there inorder to have ASP.Net 2.0 to opn my converted aspx
pages?

2.Or once i check in my converted aspx project, files , i can just package
and installl in any machine where CLR2.0 is present ?

what must be dont at the install level ?

Thanks
Senthil

[SenthilVel]

Thanks Gregory ...

one more question :

1. with my current install, the web application projects are pointed to
CLR1.1.

so i need to run the aspnet_iis tool during the install to have my web
application to point to 2.0 Right?

this will be the only steps needed , please correct me ..

thanks
Senthil
"Cowboy (Gregory A. Beamer)" <No************@comcast.netNoSpamMwrote in
message news:%2********************@TK2MSFTNGP05.phx.gbl.. .

Once you have properly converted to 2.0, you should not need anything
else. The exception is the web applications projects (originally posted
and still available at www.asp.net). This uses a more 1.x like model for
compiling the web applications with CodeBehind rather than partial
classes. Without it, you cannot compile using the older coding model.

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

*************************************************
Think outside of the box!
*************************************************
"SenthilVel" <se******************@misyshealthcare.comwrote in message
news:up****************@TK2MSFTNGP02.phx.gbl...

>Hi All

During the migration of my web project from 1.1 to 2.0 we found a web
site to have a download for a MS patch for the conversion of the web
projects to happen.

The link is :
http://msdn.microsoft.com/asp.net/re...p/default.aspx

http://www.microsoft.com/downloads/d...displaylang=en

In the local developer machines , when we want to do this conversion i
downloaded both the above and made the conversion.

My Question is :

1. In my machine where i install my web application must i also have this
downloads there inorder to have ASP.Net 2.0 to opn my converted aspx
pages?

2.Or once i check in my converted aspx project, files , i can just
package and installl in any machine where CLR2.0 is present ?

what must be dont at the install level ?

Thanks
Senthil