Should I convert from Asp to Asp.Net?

I'm developing a database in asp and i have completed a considerable part of the database.
Many people have suggested that i should have used Asp.net as the language to go.Can someone please post reasons for
1) Why should I switch to Asp.net. Is there something that Asp.Net can do and simple Asp can't?
2) I've already coded a considerable part of the database in Asp.won't it be asgaint professionalism that part of the database is in Asp and part in Asp.net?
Thanks.
theprogrammer

Check out the pro's and con's of migrating to asp.net from classic asp.
http://www.c-sharpcorner.com/Code/2004/Jan/MigratingASPtoASP.NET.asp

Matt

theprgrammer wrote:

1) Why should I switch to Asp.net. Is there something that Asp.Net can do and simple Asp can't?

Yes there are many things ASP.NET can do that ASP cannot. Why should you switch? Hell if I know. I don't have a clue what your ASP app does or if it would benefit from migration. Do you have a reason you think you should migrate?

theprgrammer wrote:

2) I've already coded a considerable part of the database in Asp.won't it be asgaint professionalism that part of the database is in Asp and part in Asp.net?

You didn't code any part of the database in ASP. ASP isn't a database language or technology. You coded your ASP application, most likely in VBScript, to work with a database. Professionalism has no bearing on this. It would be unprofessional to code your application in such a way that it didn't do the intended job. Or in a way that couldn't be modified by anyone. But having an application coded in multiple technologies is normal. You might use Javascript and even ActiveX technologies, and that certainly isn't unprofessional.
You need to look at your application and see if there is a benefit to migration that outweighs the expense in time for the conversion. If not, why migrate?
Jeff

This can be summed up with one word:

ABSOLUTELY