Re: Upgrading from asp.net 1.1 to 2.0

"Eric Dill [2005Q3]" <[email protected]>
Newsgroups gmane.comp.windows.devel.dotnet.web
Message-ID <[email protected]>
Hi Scott,
 
The problem with that is that it coverts your ASP.Net 1.1 project fine, but doesn't give you the option of building and using the ASP.Net 2.0 MasterPage option which can not be easily added in after the fact because it must be specified at page creation time and can't be added back in beyond that point in time.
 
Translation: In ASP.Net 2.0, you either begin with a MasterPage or you don't get to use the MasterPage concept.
 
BTW, I've never had a problem with the MasterPage concept in ASP.Net 2.0. The problems have always been in other areas.
 
Sincerely,
 
Eric 
 

________________________________

From: Discussion of building .NET applications targeted for the Web on behalf of Scott Guthrie
Sent: Tue 3/27/2007 11:58 AM
To: [email protected]
Subject: Re: [DOTNET-WEB] Upgrading from asp.net 1.1 to 2.0



What I'd recommend would be to use the web application project option when upgrading an existing ASP.NET 1.1 project.  The automatic upgrade wizard in VS 2005 SP1 uses this automatically - or if you don't have SP1 installed you can download the web application project download and follow the tutorial steps here: http://webproject.scottgu.com <http://webproject.scottgu.com/> 

I'd recommend first getting the ASP.NET 1.1 project building and running clean on 2.0 before taking advantage of Master Pages.  That way you have a solid baseline, and can isolate whether you are having any compat issues - or whether any issues are related to taking advantage of new features.

Hope this helps,

Scott

-----Original Message-----
From: Discussion of building .NET applications targeted for the Web [mailto:[email protected]] On Behalf Of Eric Dill [2005Q3]
Sent: Tuesday, March 27, 2007 8:49 AM
To: [email protected]
Subject: Re: [DOTNET-WEB] Upgrading from asp.net 1.1 to 2.0

Hi Alex,

The only problem I have with the VS Conversion Tool is that it doesn't utilize the new ASP.Net 2.0 MasterPage.

If you don't see any reason to build an ASP.Net 2.0 MasterPage (and use it in your project) then you can use the VS Conversion Tool, otherwise my manual process is your best option.

Sincerely,

Eric

________________________________

From: Discussion of building .NET applications targeted for the Web on behalf of Smotritsky, Alex
Sent: Tue 3/27/2007 11:30 AM
To: [email protected]
Subject: Re: [DOTNET-WEB] Upgrading from asp.net 1.1 to 2.0



Thanks Eric,

I take it you're not a fan of the Visual Studio Conversion Wizard.

Alex

-----Original Message-----
From: Discussion of building .NET applications targeted for the Web
[mailto:[email protected]] On Behalf Of Eric Dill [2005Q3]
Sent: Tuesday, March 27, 2007 10:03 AM
To: [email protected]
Subject: Re: [DOTNET-WEB] Upgrading from asp.net 1.1 to 2.0

Hi Alex,

I've done this on a few projects already and here is the approach I've
used with success:

Step 1: Decide what page elements (if any) that will move to the new
ASP.Net 2.0 MasterPage
Step 2: Create your ASP.Net 2.0 MasterPage
Repeat the following for each ASP.Net page to be converted:
Step 3: Create a new ASP.Net 2.0 page for the ASP.Net 1.1 page you want
to convert and link it to the MasterPage you created in step 3.
Step 4: Copy the HTML content from the ASP.Net 1.1 page to the ASP.Net
2.0 page (exclude any content moved to the ASP.Net 2.0 MasterPage).
Step 5: Copy the code behind page from the ASP.Net 1.1 page to the
ASP.Net 2.0 page.
Step 6: Remove all Web Form Designer generated code (this is now in a
separate file for each ASP.Net 2.0 code behind page.

Sincerely,

Eric Dill
Sr. Software Engineer
C#, .NET (ADO.NET, ASP.NET), COM+, DCOM, T-SQL, C++, C
[email protected]
703-642-1816 home
434-228-0799 cell



________________________________

From: Discussion of building .NET applications targeted for the Web on
behalf of Smotritsky, Alex
Sent: Tue 3/27/2007 10:37 AM
To: [email protected]
Subject: [DOTNET-WEB] Upgrading from asp.net 1.1 to 2.0



I'm interested in people's thoughts and experiences with this, thanks.






===================================
This list is hosted by DevelopMentor(r)  http://www.develop.com <http://www.develop.com/>  <http://www.develop.com/>
<http://www.develop.com/>

View archives and manage your subscription(s) at
http://discuss.develop.com <http://discuss.develop.com/>  <http://discuss.develop.com/>  <http://discuss.develop.com/>



===================================
This list is hosted by DevelopMentor(r)  http://www.develop.com <http://www.develop.com/>  <http://www.develop.com/>

View archives and manage your subscription(s) at
http://discuss.develop.com <http://discuss.develop.com/>  <http://discuss.develop.com/>

===================================
This list is hosted by DevelopMentor(r)  http://www.develop.com <http://www.develop.com/>  <http://www.develop.com/>

View archives and manage your subscription(s) at http://discuss.develop.com <http://discuss.develop.com/>  <http://discuss.develop.com/>



===================================
This list is hosted by DevelopMentor(r)  http://www.develop.com <http://www.develop.com/> 

View archives and manage your subscription(s) at http://discuss.develop.com <http://discuss.develop.com/> 

===================================
This list is hosted by DevelopMentor®  http://www.develop.com <http://www.develop.com/> 

View archives and manage your subscription(s) at http://discuss.develop.com <http://discuss.develop.com/> 



===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.