Upgrading to ASP.Net

#1 August 22nd, 2008, 04:05 PM

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?

#2 August 23rd, 2008, 02:35 PM

Gazing into my crystal ball I observed =?Utf-8?B?RGF2ZTEwMzE=?=
<Dave1031@discussions.microsoft.comwriting in
news:66E437FB-0534-4F57-9058-915CE9117AB0@microsoft.com:

Quote:

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?

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.

--
Adrienne Boswell at Home
Arbpen Web Site Design Services
http://www.cavalcade-of-coding.info
Please respond to the group so others can share

#3 August 23rd, 2008, 08:55 PM

"Dave1031" wrote:

Quote:

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

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.

#4 August 24th, 2008, 10:45 PM

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.

Upgrading to ASP.Net

re: Upgrading to ASP.Net

re: Upgrading to ASP.Net

re: Upgrading to ASP.Net

/bytes/development

/bytes/it

/bytes/about