Upgrading to ASP.Net

D

Dave1031

I know I am quite behind the times but I need to finally upgrade our website
from classic ASP 3.0 to ASP.Net.

I plan on creating apsx pages with the same names as the old asp pages.
Then remove all of the code from the old asp page with the exception of a
Response.redirect to the comparably named apsx page.

Is this pretty much standard practice when upgrading?

Any insights from someone who has done this?
 
A

Adrienne Boswell

Gazing into my crystal ball I observed =?Utf-8?B?RGF2ZTEwMzE=?=
I know I am quite behind the times but I need to finally upgrade our
website from classic ASP 3.0 to ASP.Net.

I plan on creating apsx pages with the same names as the old asp
pages. Then remove all of the code from the old asp page with the
exception of a Response.redirect to the comparably named apsx page.

Is this pretty much standard practice when upgrading?

Any insights from someone who has done this?
Click to expand...

If you have an include that all the pages use, that might be at the top
before anything is written out to the client, you could put the
information there. I would suggest, however, using a 301 response code,
that will tell search engines that this is a _permanent_ redirect.
 
O

Old Pedant

Dave1031 said:
I plan on creating apsx pages with the same names as the old asp pages.
Then remove all of the code from the old asp page with the exception of a
Response.redirect to the comparably named apsx page.
Click to expand...

There is a possible major problem with this approach: If your ASP pages
depend in any way on session variables, then you won't be able to convert
piecemeal. You'll have to do it all at one time. That's because ASP and
ASP.NET don't share session variables.

If you were planning to do an all-at-once replace, anyway, ignore this
little man in the corner.
 
D

Dave

Thanks guys.

I found the following example on http://www.somacon.com/p145.php

<%@ Language=VBScript %>
<%
' Permanent redirection
Response.Status = "301 Moved Permanently"
Response.AddHeader "Location", "http://www.somacon.com/"
Response.End
%>

....but it never seemed to effect the redirect so I ended up using this...

<%@ Language=VBScript %>
<%
Response.Redirect "default.aspx"
%>

<html>
<body>
<p>Page moved</p>
</body>
</html>

...which seems to work fine unless there is something I 'm not aware of?

The session variables are not an issue (although I did notice that the
session id is no longer an int but a varchar and it seemd to change with
every page request. What's up with that?).

Thanks
Dave.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

How to retrive payment result value after secure paytabs payment done in PayTabs payment gateway in asp.net 0
Upgrading HTML to ASP.NET 2.0 2
Hello all! Noob here with completely unrealistic ambitions. Happy to join the crew and get good enough to help others. 4
SQL, XML, and ASP.NET: Upgrading from a client-side heavy classic ASP app 6
Simple web framework - improvements to makefile 0
Errors after upgrading SQL Server 2000 database compatibility level 3
problem upgrading to JSTL 1.2 11
Framework 2.0 performance problem when upgrading dll in productionenvironment 0

Members online

Total: 35 (members: 2, guests: 33)
Robots: 268

Forum statistics

Threads
473,997
Messages
2,570,239
Members
46,827
Latest member
DMUK_Beginner

Latest Threads

Top