Perlscript is an ActiveX extention, provided by Activestate. Since perlscript is a client-side language, the end user must have the activeX component on thier systems for perlscript to work.

Its really meant for things like automation, or building apps where you control the end users environment. I imagine you can embed the ActiveX control in the browser (in the case of IE only) but ... really kinda an ugly way to go.

theAcolyte

Activestate dixit: PerlScript is an ActiveX scripting engine that allows you to use Perl with any ActiveX scripting host. At this time, ActiveX scripting hosts include:

• Internet Information Server 3.0/4.0/5.0
• Peer Web Services 3.0/4.0
• Microsoft Internet Explorer 5.0x
• Windows Scripting Host

In other words, PerlScript can act a a scripting engine on either side (client or server):

Client-side

Perlscript may be use like VBScript or JavaScript in html pages and runs in the context of the browser.

Server-side

The scripting engine is driven by the web server (IIS) in order to generate html to be send to client browser (like PHP).

Pages sources may become difficult to read if they both are server-side generated and contain client-side script...

Javascript runs. I haven't tried VBScript. This is what I get
URL: http://e9ew8/PerlScript/ado10.asp
Active Server Pages error 'ASP 0201'
Invalid Default Script Language
The default script language specified for this application is invalid.
The default script language is PerlScript. I set it in IIS for the PerlScript virtual directory.
If I don't set it, I get a different but similar error message.

This is possibly because PerlScript was not registered as an ActiveScripting provider when you installed Perl - you can check this by opening regedit and looking for a key:

HKEY_CLASSES_ROOT\CLSID\{F8D77580-0F09-11D0-AA61-3C284E000000}
[download]

This should have have an InProcServer sub-key with a value of c:\perl\bin\perlSE.dll as well as an OLEScript key.

You could hand edit the registry to put this in - (you will also need to set the correct ImplementedCategories key) - but the easiest way to remedy is to reinstall ActivePerl

/J\

Update: Based on theAcolyte 's reply to my post, I revoke this statement, and offer apologies. If the OP had asked about Client-side scripting (Why would he want to do that in perl?), his reply is valid.

The .asp files need to be server by a WEB SERVER, such as IIS.

The client browser is irrelevent. What the web server does is convert/run the asp code (regardless of whether it is Javascript, VB or perl), and send HTML to the browser.

What you need to do is to place the asp code on a web server (which could be your own machine), and view it using a URL pointing to that page within the server.

Your URL should NOT be something like C:\pathname\file.asp - that will be served by the file system, not by the web server.

Your URL should be http://Servername/pathname/file.asp

Um ... no, its not wrong (my answer). The orignal question said:

My .asp files containing perlscript don't run in either IE or Netscape.

So I'm assuming the poster means Client-Side perlscript (to be executed in the browser) ... and to quote from the activestate documents:

Client-Side PerlScript has Perl embedded within your HTML documents. All PerlScript code must be contained within <SCRIPT LANGUAGE="PerlScript"> </SCRIPT>
 
Client-side PerlScript has the added requirement that both ActivePerl and PerlScript be installed on each computer will will be loading PerlScript pages.

So I guess the client browser isn't irrelavant, eh? If the poster meant server-side perlscript (and I misunderstood) then you are right and the poster needs to look at an ASP manual to get things working right

theAcolyte