I have write mod_perl code. Write perl modules that I in mod_perl. Get good results using mod_perl.

For me, one big disticntion between the two is that my mod_perl environment is completely Open Source. My ASP environment was a mix of open and closed source. For some that is no big deal but for me OSS is my salvation and on that basis alone I will go the Perl-mod_perl-Apache route before I will go the ASP-IIS route ever again.

The biggest disadvange that I see with the Perl-mod_perl-Apache route is that you will need to roll a number of your own pieces and strategies. Whereas the ASP/IIS world has already sorted out a few of the complicated details for you. Sessions come to mind. It is considerably more involved to set up effective session management on the Perl-mod_perl-Apache side than it is on IIS.

The big plus to counter the implementation complexity is flexibility and the chance to understand EXACTLY what's being done and where it happens in the code. As someone who has to get a job done you have to choose which path is best for your situation.

The one thing to consider is that going the OSS route may not only be better for you but I feel it is better for our society in general.