Running perl without a command window

Mattk470 has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Running perl without a command window by Mr. Muskrat (Canon) on Oct 24, 2002 at 22:27 UTC
On Win32 systems with ActiveState Perl, you can associate a certain extension with the wperl interpreter. I use the .wpl extension for that purpose. Just rename the script with the new extension and double click on it. Windows will ask you what program you want to use to open the file. Click on the 'Other' button. Browse to where you have Perl installed and choose the wperl.exe file from the bin directory.	[reply]
Re: Running perl without a command window by ff (Hermit) on Oct 25, 2002 at 03:27 UTC
If you are using 'perlapp' to create .exe files from your .pl source, you can try including '--gui' in your builds. I posted a question related to yours earlier this month at ActiveState wondering why passing parameters when invoking 'abc.exe' programs was failing. I had been creating via 'perlapp --gui abc.pl' and my memory says that when I stopped including '--gui' in my builds, I could then pass parameters. But then I got the silly console window back. Jan Dubois had posted back that: Basically --gui for PerlApp has the same effect as switching from perl to wperl. If something doesn't work with wperl, then it most likely won't work with "perlapp --gui" either (and can't be fixed inside PerlApp).	[reply]
Re: Running perl without a command window by Silicon Cactus (Scribe) on Oct 25, 2002 at 15:19 UTC
Are you building a GUI app? or a service? or what? If you are building a GUI app, hiding the DOS window is definately an option. Otherwise, scheduling is a possibility.. Without more information it is difficult to help you.	[reply]