The answer is, of course : does the application still serve its purpose ?
If your ASP 3.0 application can handle the needs of its clients,
there's absolutely no need to migrate it to ASP.NET 2.0.
The largest benefits ASP.NET 2.0 offers, besides architectural and
code management considerations, are its scalability and efficiency factors.
ASP 3.0 runs on interpreted languages so it's noticeably slower than ASP.NET 2.0,
although a bit more efficiency can be obtained by compiling code to dll's either with
C++ or VB6.
But, whenever you need to change any compiled code, you have to stop your whole site.
ASP.NET 2.0 delivers much more throughput because, after the initial compilation,
your site is running from memory. Also, you can hot-swap assemblies.
There is no "end of lifecycle" for ASP. You can use it from here to eternity if you wish.
MS support for it will end at some point in the future, though.
You should only migrate your applications if you need better performance
than you're getting ( if the website is choking on too many visitors, for example )
or if you will benefit from the management advantages that OOP provides.
Those are the key improvements which ASP.NET boasts over ASP 3.0.
Juan T. Llibre, asp.net MVP
aspnetfaq.com :
http://www.aspnetfaq.com/
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
===================================