I write a perl script and turn it into a Windows executable, using pp on a PC with ActiveState Perl and all the right modules.
Then I test it. It works fine. Does it work fine on another PC without Perl and half of CPAN on it?
My testing normally involves moving it to another, more benighted PC, but there's got to be a smarter way!
How can I test it on the same PC? Empty out @INC somehow?
($_='kkvvttuu bbooppuuiiffss qqffssmm iibbddllffss')
=~y~b-v~a-z~s; print
'Does it work fine on another PC without Perl and half of CPAN on it? '
Did you read the documentation to find out how to package the modules (along with their dependencies) your script uses?
Martin
If a .dll is needed depends on the moduls used in your script.
The best way to test it is to have to different PCs (one development and one "standard") or to run two different OS on one PC...
You can do that if you have some virtualization application like Vmware... but probably it will be more expensive than having another box with MS Windows installed.
I never tried, but you may try to change PATH variable (and probably @INC too) using a command prompt session to test and restoring it after testing. You could do the same with DLL (like renaming, moving or unregistering it before testing).
---------------------------------
"You have enemies? Good. That means you've stood up for something, sometime in your life." - Sir Winston Churchill