Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jan 03, 2013 12:13 AM by Careed
Jan 02, 2013 11:38 PM|LINK
In the current way that companies buy other companies and then leave it up to IT to figure out how to make smooth user interface out of the outdated application...
We have been given the task of migrating and updating a web site that looks like it was written in classic ASP with Fremework 1.1 and has not been updated since it was originally written (new pages by date in remarks, but same format in pages <% ... %>).
It is running current on a Windows 2000 server which we would also like to upgrade to one of our Windows 2005 servers once we have the web site working in at least Framework 2.0.
Would love to get some suggestions as to how to proceed. Some of what I have read said it is possible to migrate from v1.1 to 4.0. But I am not sure how much work will be involved after the migartion to correct allof the errors. Thank you for any recommendations.
Jan 03, 2013 12:13 AM|LINK
First of all, it's not actually classic ASP if it's using ASP.NET 1.1. Likely, it's a hybrid attempt to move to .NET from classic ASP.
As for upgrading, frankly, rewrite it from scratch. You will likely spend less time building the app from scratch than you would trying to retrofit it to ASP.NET 4.0. In the long run, you'll likely improve the application with a complete rewrite; otherwise,
you will have an application that is put together with chewing gum and chicken wire.