I agree that porting from ASP to ASP.NET is brutally hard, and usually forces a total rewrite unless you want “worst practices” code. You’ll get no argument from me there.
I still think it’s worth it for your flagship applications, however. ASP is just so primitive.
I mean it is just a Recordset.Open type of application. It will gain nothing from the port.
It’s his company, obviously, but I don’t agree there is “nothing to gain” even if you did a basic Reponse.Write port of an ASP site. Just having a properly functioning debugger and breakpoints-- which I don’t ever recall having in InterDev-- would be worth it as far as I’m concerned. I could probably name ten “bet the company” reasons you would want your flagship app on ASP.NET instead of classic ASP. And as Drazen pointed out, the least of those reasons is that ASP is on life support already…