Port ASP 3 to ASP.NET

[Steven Garvin]

Hi,

We currently have an ASP 3 application which we would possibly like to
upgrade to ASP.NET. Previously I have painstakingly ported each page
using a combination of the ASP Migration Assistant and trawling
through the files changing syntax, etc.

My question is this: is there really any point to this? To take full
advantage of .NET would it be better to redesign the application
(regardless of whether or not this is economically viable at present)
and start from scratch ending up with a fully .NET compliant
application.

By simply (!) migrating the code, are we gaining anything over just
running the ASP 3 application with Win2003/IIS6?

Thanks in advance,

Steven

 

[Kevin Spencer]

Hi Steven,

There may be some controversy about this, but I would tend to agree with
you. ASP is procedural in nature, while ASP.Net is object-oriented. ASP has
limitations which must be augmented with COM objects, while ASP.Net employs
the full spectrum of the Common Language Runtime Library. It is hard to
imagine that simply converting pages would yield positive results; an
architectural re-design would most likely be the best route to go.

On the other hand, ASP.Net being much superior to ASP, you did manage to get
a good education in the new technology, so it wasn't wasted effort by any
means!

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.

 

[Chad Z. Hower aka Kudzu]

A better approach might be to migrate one page at a time and have the ASP
pages post/redirect into ASP.net, and so on.