Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • PerlApp extracts to a temp directory, and I'm fairly certain perl2exe does too (unless either of these programs have changed this in the last couple of versions).

    And, even if they do, I don't quite see what's to get upset about that.

    I'd stick with PAR if I were you.

    And I'm trying to remember which win32 utility we used to use for deploying software to 20+ Windows load generating machines during performance testing, but I really can't seem to squeeze it out of my head... :/

    It was rather good anyway, since it
    • And, even if they do, I don't quite see what's to get upset about that.
      I consider it quite unprofessional. For example, it would be enough to stop me from thinking of building a program for distribution on CD-ROM, that is to be run directly from the CD, with it.

      I'd stick with PAR if I were you.
      I've only briefly tested PAR, and not recently, but just to be fair, I might test it again to compare it with the others.

      And I'm trying to remember which win32 utility we used to use for deploying software to 20+ Windows load generating machines during performance testing, but I really can't seem to squeeze it out of my head... :/
      Of, I would be so grateful if you could think of what it was... I've found a few possible solutions, but fewer options than I would have expected, and none that really pleases me:
      • I can put it in a Startup script, assigned to the computer [microsoft.com] in a Group Policy in Active Directory, so it runs when the computer boots
      • I can pretend that it's a program installer by producing a ZAP file [microsoft.com] that can be attached to a Group Policy [microsoft.com] in Active Directory, to be run at logon. Oddly enough (IMO), you can attach installers (MSI files, or ZAP) to group policies, but no ordinary executables. In that case, a ZAP file wrapper looks like the easier solution to me.
      Tips for other solutions are most welcome.
      • Meh, .ZAP files don't work for installation deployment in Active Directory. It requires that it's an .MSI file.

        I just though I'd add it here so people searching with Google for a solution for the same problem won't get their hopes up too high.