you mean the way PerlCtrl can create a single EXE for running on a machine without Perl?

Yep - sorry I wasn't very clear on that point. The Perl Dev Kit makes for more distributable applications - especially components.

That is if you don't mind distributing components that are around 1mb or more :). You can do it without freestanding mode and have a nice dll around 30k. I worry whenever I see components that are much more than 100kb. It's understandable why they are so big with PerlCtrl - it is compiling perl along with it!

On the other hand, if you know your target machines are running Perl - I see no reason not to use WSH to create a component. You can always copy and past the code into a PerlCtrl template at a later date.

One other thing I haven't looked into in much detail is the licensing for the Perl Dev Kit. I am pretty sure that you can distribute your applications without worrying, but I imagine that you're only meant to install it on one machine at a time. At least with WSH you can develop your component on any Win32 machine running Perl.

By the way, do you think anyone would be interested in an Inline::WSH module?

Error: Keyboard not attached. Press F1 to continue.