Doesn't the PerlNet component just link the native Windows version of Perl with .NET with a bit of glue to allow them to call each other?
Perl is not running on the .NET VM, is it?
then if you use Perl on .NET it won't be portable to other platforms
Er, maybe im confused by what you mean by this, but the previous two answers (which you asked rhetorically, so you know this already) clearly indicate that the perl code you write using the .NET IDE, so long as it doesnt utilize other .NET features should be just as (non)portable as the same code written using Emacs, Ultraedit or the commandline. Why should the fact that youve used the activestate IDE change anything?
Yves / DeMerphq