On 29/07/2010 23:32, Jan Dubois wrote: > On Thu, 29 Jul 2010, Lyle wrote: > >> I've love to know how to get this working, or if it even works at >> all. Someone already started a forum post on this, but with no response. >> http://community.activestate.com/forum-topic/help-windows-2008-server-asp-perlscript >> I tried adding perlis.dll to the ISAPI filters and the ISAPI and CGI >> Restrictions, but then my 500 became:- >> >> >> HTTP Error 500.19 - Internal Server Error >> >> >> The requested page cannot be accessed because the related >> configuration data for the page is invalid. >> >> So I'm guessing I've missed something or perlis.dll doesn't work for >> IIS7. Seeing that the source for perlis.dll isn't public, I've hit a bit >> of a dead end :( >> > PerlScript and Perl for ISAPI are different things. >
I'm curious as to the mechanism from which the ASP script recognises PerlScript? > However, both PerlScript and the Perl for ISAPI plugin (as well as PerlEx) > only work with 32-bit IIS, so you will need to enable 32-bit application > support for your App Pool. > Hey that worked :D > Caveat: I'm only guessing here, I haven't actually tried running 32-bit Perl > on top of 64-bit IIS, so I don't know if it really works or not. > Is proper 64-bit support planned? It's all XML config files, so I would have thought having the ActivePerl install create the file mappings, etc, wouldn't be to hard... Or are you waiting for the 64-bit Perl on windows to mature more? Lyle _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
