02-19-2007, 06:24 PM
Am now faced with a new project and it is requiring me to "modify" an existing website and "migrate" it from classic ASP to ASP.Net.
This is the first time I will be attempting to do this.
How simple/complex is this task? I have thought of rebuilding the whole site from the ground up but the time constraints simply won't allow that.
Any ideas on how to do this?
thanks for all answers.
btw, I have no previous experience with classic ASP :whoops:
02-20-2007, 08:44 AM
The only way is to start from the ground up. The way classic ASP applications were built have nothing in common with the way .NET applications are built. Period.
02-21-2007, 10:56 PM
shoot.. no migration wizard? not even for 2005?
02-22-2007, 06:03 AM
Since ASPX operates on a totally different framework there is no type of migrations whatsoever. There are also reasons like the spaghetti coding of classic ASP that make it impoosible to do a conversion. I have Classic ASP experience and I am just getting acclimated with ASP.Net and I can tell you they are nothing alike (I am saying that cause I saw you mentioned you have no former classic ASP experience).
Good luck! The organization funding the project will have to come to the fast realization that it will need to be designed from the ground up.
I have a small application I use for my job function that I created in Classic ASP it is only about 20 pages... even that needs to be totally redesigned in ASPX.
02-22-2007, 03:44 PM
Shoot.. well I have already evaluated the pages and passed the report and some support documents (I'm tempted to include your replies) that should help the company re-consider.
Thanks for the replies guys..
02-23-2007, 12:31 AM
er.. follow-up question:
What if I construct the New pages in .Net and keep the old ones in asp? What issues do you think I will face in that scenario?
02-23-2007, 07:04 AM
You can do that. It all depends on how you are exchanging data from page to page. If your pages can be considered primarily independent of one another then you would be fine.
I have done something like this... for example I have all my old update/add pages in ASP (lack of time to covert) and I have my display pages in ASP.Net due to the ease of sorting, searching, etc. I use Session Variables to manage logins so that has not changed either...
02-23-2007, 11:53 AM
I use Session Variables to manage logins so that has not changed either...
Be careful with this one...
You cannot directly share session variables between Classic ASP and ASP.NET pages. There are tricks you can use to get around this (see Google), but it's ugly.
02-23-2007, 12:27 PM
I would like to hear a little more about this one since I am using asp and asp.net in the same web app and I am having no issues.
02-23-2007, 04:52 PM
Yes, some members of the old team said that the Session variable declared in classic asp cannot be referred to as readily as those declared in asp.net?
But it should still be Request.QueryString for string variables right?
02-23-2007, 05:14 PM
Yes, that I can assure you that Request.QueryString and Request.Form will work....
Now obviously handling the strings once captured is TOTALLY different.
02-23-2007, 05:22 PM
SO, in my .Net code, I can do something like a
Response.Redirect("nextpage.asp?&value=" & txtName.Text)
or something like that?