Don't throw it out... just do as suggested and seperate the logic. Apache::ASP can handle this very nicely.
In your global.asa file, (and other includes) make your business logic, including functions that return the data needed to display on a page.
In your asp pages, keep the logic simple; just simple loops to build the html structures needed, stuff like that. It should be mostly html. Use includes to refactor html that appears on multiple pages. Heck, asp includes can even take parameters that can be used to customize the file being included.
I'm using php4, mod_perl, and Apache::ASP all in one server. Having tried several languages, I'm moving everything over to Apache::ASP, because it combines perls rich modularity (CPAN) and mature language with the ease of ASP's sessions and web handling.
Here's my configure line for apache...(1.3.x) it doesn't build everything for you, but it seems like it is the hardest step.
'./configure' '--prefix=/usr/lib/php' '--with-imap=../imap' '--with-my +sql' '--with-zlib' '--with-apache=../apache_1.3.27' '--with-gettext' +'--enable-track-vars' '--with-db3' '--enable-bcmath' '--with-config-f +ile-path=/usr/local/apache/conf/' '--with-ldap=/usr' '--enable-ftp' ' +--without-gd' '--with-mcrypt'
Oh, it also has ssl built in... I guess the configure script found it automatically.