You can serve perl CGI scripts with IIS, just like you would on a unixish system. On unixish systems you have a shebang that tells what program should execute the perl script: #!/usr/bin/perl
In IIS on windows you use the extension of the perl script (e.g. ".pl", or whatever you choose) to decide what program should execute the perl script. In IIS you can decide this on a per directory basis. Here is a quote from the ActivePerl documentation for Perl 5.005_03 (HTML docs: ActivePerl FAQ->Web Server Config):
"....
From the tree display on the left, select the level at which to apply the mappings. You can choose an entire server, web site, or a given virtual directory.
Select Properties from the Action menu.
If you chose to administer the properties for the entire server, the Server Properties dialog will appear. Select WWW Service from the Master Properties pull-down menu and click the Edit button under Master Properties. This opens WWW Service Master Properties. Select the Home Directory tab and proceed to step 7.
If you chose to administer the properties for an entire web site, the Web Site Properties sheet appears. Select the Home Directory tab and proceed to step 7.
If you chose to administer the properties for a virtual directory, the Virtual Directory Properties sheet appears. Select the Virtual Directory tab and proceed to step 7.
Click the Configuration button. This opens the Application Configuration dialog.
Select the App Mappings tab and click the Add button. You see the Add/Edit Application Extension Mapping dialog.
To run Perl as a CGI application, type the full path to Perl.EXE followed by %s %s. When a script is executed, the first %s will be replaced by the full path to the script, and the second %s will be replaced by the script parameters.
..."
/jeorgen |