Just a quick question about ease-of-use regarding Wise Package Studio and InstallShield 2011.

At my previous employer, we used Wise Installation Studio to repackage software and distribute. Obviously, that product is no longer valid since Symantec doesn't even list it on their Downloads page. So, I'm now looking at Wise Package Studio and, because of recommendations, InstallShield 2011.

But here's the rub. I don't need to create detailed installers. I'm looking more for a scripting tool, such as WiseScript Editor but more robust, such as the capabilities in Wise Installation Studio. WIS was so easy to use because all of the choices were laid out for you; no need to have any real scripting experience. I can't find anything as simple in WPS or IS. Those apps want me to create detailed installers, e.g. Add/Remove programs, components choices, etc. Really, I'm just looking for a glorified scripting editor.

I noticed that WPS does contain WiseScript, I just had to go digging through the folders to find it. Does IS shield have the same easy-to-use script editor? What do you guys suggest?

An example of the type of job I need: A script that prompts a technician to input their credentials and some other information, applies that information to the registry, does some configuration changes on a client machine, and then outputs a text file (build report) containing what was done on the machine. In WIS or WiseScript, that's easy enough to build. WPS or IS? Not so much. (At least, not as far as I can tell.)

Again, I need a down-and-dirty script editor, not a robust solution. I'm not really packaging software; I'm creating scripts.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


If your requirement really is as simple as that, you don't need to spend thousands of [insert your currency here] at all. My own preference for jobs like you outline is HTAs/VBScript but am slowly weaning myself on to PowerShell. For VBS, the natty PrimalScript provides IntelliSense/AutoComplete/whatever_MS_is_calling_it_this_week. I haven't come across anything similar for PS but haven't looked that hard because I prefer a simple editor.
Answered 10/30/2010 by: VBScab
Red Belt

Please log in to comment
Thanks for the tips. I've download the PrimalScript tools and I'm slowly working my way through using Powershell. One dilemma I've run into is that everything I've read says a Powershell script can not be turned an EXE or otherwise "clickable" script. Is there a way to "wrap" the script? (The machines that will be running the script don't have Powershell on them but I intend to circumvent that by simply installing it during the image build process.)
Answered 11/03/2010 by: FNO1980
Yellow Belt

Please log in to comment
if this is during a build process your best bet is c# if the boxes is Vista or later.

If it is prior to that your stuck with vbs and hta. You can encode vbs etc if your trying to mask the code for some reason.
Answered 11/03/2010 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment