Envoy2064
asked on
Stand-alone Perl.exe version for CGI executables in IIS?
Hi,
I'm looking for a stand-alone version of Perl.exe for Windows so that my CGI script in IIS server can run without having to install the ActivePerl program on the production server. Is this possible? The CGI script needs the following libraries:
use Win32::ODBC;
use CGI qw(:standard);
use File::stat;
use Time::Local;
Any help will be appreciated!
I'm looking for a stand-alone version of Perl.exe for Windows so that my CGI script in IIS server can run without having to install the ActivePerl program on the production server. Is this possible? The CGI script needs the following libraries:
use Win32::ODBC;
use CGI qw(:standard);
use File::stat;
use Time::Local;
Any help will be appreciated!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
it is possible to install ActivePerl on the production machine with as little impact as possible?
Not sure what you mean by "as little impact as possible".
If you are concerned that installing ActivePerl might cause other things to stop working, I wouldn't be very concerned. It is very common to have ActivePerl installed on production servers.
Installing ActivePerl will:
* create a directory (usually c:\perl) that will contain all of the perl files (the perl interpreter executable, libraries, etc.).
* It will create an association between .pl files and the perl interpreter (usually c:\perl\bin\perl.exe)
Then you may have to enable perl in IIS - I'm not very familiar with IIS.
Then you may have to install additional perl modules, if you are using any that don't come as part of the standard distribution. This can usually be done using ppm - and doesn't require anything else be installed. Occasionally (very uncommon on windows) you will need to have a compiler installed.
There shouldn't be many other changes needed to your system though.
If you are concerned that installing ActivePerl might cause other things to stop working, I wouldn't be very concerned. It is very common to have ActivePerl installed on production servers.
Installing ActivePerl will:
* create a directory (usually c:\perl) that will contain all of the perl files (the perl interpreter executable, libraries, etc.).
* It will create an association between .pl files and the perl interpreter (usually c:\perl\bin\perl.exe)
Then you may have to enable perl in IIS - I'm not very familiar with IIS.
Then you may have to install additional perl modules, if you are using any that don't come as part of the standard distribution. This can usually be done using ppm - and doesn't require anything else be installed. Occasionally (very uncommon on windows) you will need to have a compiler installed.
There shouldn't be many other changes needed to your system though.
ASKER