ASP.NET vs Classic ASP? If you're using both to write simple web sites, well you may as well stick with Classic ASP, but then ASP.NET is pretty much a superset of Classic ASP anyway, so what's the problem with using ASP.NET as you would Classic ASP and only using the bits of ASP.NET that you need?
ASP.NET is not supposed to be a replacement of Classic ASP with regards to allowing you to write similar stuff to the sites you've been used to, it's to allow you to write the next generation of web applications, for which Classic ASP is just not a reasonable choice. It's not just the development of the application either, it's how a web application is presented to the users with regards to performance and robustness. As web applications get ever more complex, you need a solution that offers high performance, strong security and robustness designed in from first principles. Classic ASP might be easy to write a basic app in but it's hopeless for enterprise level web applications and as good as programmers can be at tweaking Classic ASP to do what they need, ultimately most realise that Classic ASP has serious issues when it comes to anything but the simplest web applications. As the demand for richer content and more functionality grows, these issues will become ever more painfully obvious. That's why ASP.NET is the future and that's why the learning curve is so much steeper, because the benefits of ASP.NET in terms of fulfilling the enterprise's requirements, are so much greater.
