ASP to ASP.NET conversion

Right now I'm working in a with asp classic, mostly due to the fact that my boss (who would need a lot of convincing to learn another prog. language) wants to be able to understand/edit/troubleshoot any code I make, along with other reasons.

For my own purposes, and a few frustrations with asp classic, I've been wondering if it'd be worth it to me to go ahead and learn it, then see if I can present the benefits to my boss with first-hand experience in it.

Anyway, questions are, is there anyone who has made the switch? Is it worthwhile? And how true is the backwards compatibility factor?, can I pretty much just copy over all the existing code and have it running with minimal changes?

This is an asp vs asp.net question, so don't bother with a php (or other AST) conversion suggestion, it won't happen.

>>3 you can split the main HTML code and the server side code into separate files
OP here, that sounds extremely useful, didn't see anything about that in what I've read. I'm setting up a test server with asp.net enabled... I'm gonna mess around with it some.

>>2
>>4
I'd be lying if I said I didn't see that coming x_x