Re: Re: Last Script. What now?

AFAIK PerlScript is NOT what you want to use with ASP.Net. You don't use VBScript either, you use VB.NET. What you want is PerlNET.

I did not try it yet but I'd bet it would be best to the the interface related stuff in VB.NET or C# (simply something supported natively by Visual Studio.Net) and only use PerlNET to either implement things that are much easier written in Perl than in the .Net languages or to wrap up the functionality of some CPAN module.

Jenda

Comment on Re: Re: Last Script. What now?

Replies are listed 'Best First'.
Re: Re: Re: Last Script. What now? by Theseus (Pilgrim) on Nov 29, 2002 at 21:15 UTC
PerlNET AFAIK is just a program developed by activestate to help develop Perlscript.NET components, not the actual language itself. However, I do agree with you about what I would use Perl for in a .NET scenario, I'd stick with C# for most things and switch for things simply too much easier to do in Perl to ignore, and to take advantage of CPAN modules.	[reply]
Re: Re: Re: Re: Last Script. What now? by Jenda (Abbot) on Nov 29, 2002 at 21:43 UTC
Sure. PerlScript is not a language either. PerlScript is just the "Scripting Engine", the PerlSE.dll. In both cases the language is Perl. Jenda	[reply]