On Tue, 01 Apr 2008, Howard Maher wrote:
One of our possible vendors said that if Perl scripts can be callable
COM objects, then we can interface with their engine. Does anyone know
whether Perl scripts can be? The languages that they suggest are VB6,
C++, and .NET...
Perl code can be wrapped as an OLE Automation compatible object (IDispatch)
using either Windows Scripting Components (use the PerlScript engine included
in ActivePerl), or with PerlCtrl (part of the ActiveState Perl Dev Kit).
http://aspn.activestate.com/ASPN/docs/ActivePerl/5.10/Windows/WindowsScriptComponents.html
PerlCtrl allows you to create a single standalone DLL that contains all code
necessary to execute your Perl code; no separate Perl installation is necessary.
http://aspn.activestate.com/ASPN/docs/PDK/7.1/PerlCtrl_overview.html
The Perl.NET project has pretty much been scrapped, correct? Thanks in
advance for any help you can give us.
The Perl Dev Kit also include PerlNET, which allows you to implement .NET
components written in Perl. A bug in recent .NET updates prevents some
PerlNET code to run with the latest .NET; this problem has been fixed in
PDK 7.2 to be released later this week.
PerlNET will allow you to implement other COM interfaces and is not limited
to IDispatch. You'll need to understand .NET/COM Interop to make use of this
though.
http://www.activestate.com/Products/perl_dev_kit/index.mhtml?_x=1
http://aspn.activestate.com/ASPN/docs/PDK/7.1/PerlNET_overview.html
Note: The PDK 7.1 release does not contain PerlNET because we did not have
a workaround for the bug in the latest .NET framework in time for the release.
Cheers,
-Jan
___
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
