I'm in the exact same situation as you. I love Perl, and started that at my company, but they've been making me systematically recode all my old perl web apps in C#.NET. I have to say, after learning ASP.NET and C#, I definitely see Perl in a new light. If I had to sit down today and start writing a web app of my own, I'd definitely want to write it in ASP/C#.net, but I still find uses for Perl, without a doubt.

Next time your boss needs one of those beautiful Microsoft IIS log files examined in detail to search for something, or to munge data from it, you'll be able to show him exactly what place Perl has in your organization. It may not be the best thing for web development any more, and in reality, that's not what it's intended for, it shouldn't surprise anyone that ASP.net is more efficient for web applications.

I still write scripts to do remote backups on servers with Perl(I'm not into server administration either, but our IT department relies on the development department to design them tools), I still write text processing scripts in Perl, I find a way to work it in for most things I have to do that aren't web-based.

As far as everyone suggesting Perlscript for ASP.NET, you might as well not even bother. The current state of affairs is horribly broken. I posted on Perlmonks about 2-3 months ago several times asking for anyone's advice or experience with Perlscript for ASP.NET, and apparently, you and I are the only two monks who are even remotely interested.

There would be nothing more powerful than the tools that ASP.NET puts into your hands with web controls, the .NET Framework Class Library, and CPAN all rolled into an integrated solution. I salivate at the mere thought, but then I remember that it just doesn't work. If we're all lucky, Microsoft will recognize that Perl isn't a toy language and they'll really put some effort into support and documentation for it.