There is no need to abandon perl when you move to .Net.

ActiveState ASPX claims:
ActiveState PerlASPX enables professional Perl programmers to use Perl for dynamic content generation on ASP.NET Web servers.

Built on the .NET framework, PerlASPX adds Perl to the list of supported ASP.NET languages. PerlASPX leverages the power of ActiveState PerlNET to deliver a flexible option for programmers who prefer Perl for its powerful text processing capabilities, or have legacy Perl code. PerlASPX also enables programmers to create ASP.NET-hosted XML Web services in Perl.

I haven't used ActiveState perl.Net, but have programmed web pages in C#, after years of plain ASP/VB programming (Prior to obtaining Perl enlightenment). The Visual Studo tools are great for building pretty and functional web pages.

I was plesantly surprised to find .Net's approach very similar to using Perl modules - apparently M$ learned a lot by stealing a delphi programmer.

It is very important that you get .Net infrastructure training first - to understand the underlying architecture - basically, it is a virtual machine, and you need to figure out how the "module" equivalents are loaded and stored in the global assembly cache.

C# is actually a nice language (Not as powerful as Perl), which does not suffer from C++ bloat.

re: Books - MS Press has tons, as does Orielley - sorry names escape me - & I did not pay much attention to the books - in my case the intro to architecture class was great, and on-line tutorials +Hands-on were way better than the books.