Moving away from WiseScript
Hey Guys,
I'm currently on a project where we're contemplating the move from Wise Package Studio to Installshield. Having worked with Installshield extensively over the past years, I have the actual packaging aspect of it pretty much covered.
However, the current packaging process involves extensive use of WiseScript to create Install Wrappers for the different packages. Moving away would also mean looking for a viable alternative for these.
Do any of you have any hands on experience making this move? What were the issues you ran into? What other options did you consider and choose, and how did you go about the actual move?
Your insights will be greatly appreciated,
PJ
I'm currently on a project where we're contemplating the move from Wise Package Studio to Installshield. Having worked with Installshield extensively over the past years, I have the actual packaging aspect of it pretty much covered.
However, the current packaging process involves extensive use of WiseScript to create Install Wrappers for the different packages. Moving away would also mean looking for a viable alternative for these.
Do any of you have any hands on experience making this move? What were the issues you ran into? What other options did you consider and choose, and how did you go about the actual move?
Your insights will be greatly appreciated,
PJ
0 Comments
[ + ] Show comments
Answers (13)
Please log in to answer
Posted by:
daniel.soller
7 years ago
see here: http://www.scriptingframework.ch/
this is a very good tool
Posted by:
anonymous_9363
12 years ago
Pieter, are you on Symantec Connect? It has what is possibly the worst UI of any forum/portal on the planet but one of the moderators, EdT, is likely to be able to help you out but post in the 'Wise Packaging' forum generally.
While you're waiting for a response, you can enjoy the equally brain-dead questions that get posed there, too.
While you're waiting for a response, you can enjoy the equally brain-dead questions that get posed there, too.
Posted by:
mstegginamani
12 years ago
I will let you know more on this after some time.
Thanks,
-MST
Posted by:
pjgeutjens
12 years ago
Pieter, are you on Symantec Connect
I've been there a couple times. The UI tends to give me a bit of a headache, but I'll give it a go.
Thanks for the tip.
PJ
Posted by:
pjgeutjens
12 years ago
I think I managed to post to Symantec Connect...
And now I have a headache... what an absolutely roundabout way of posting a new forum topic..
Also I cannot seem to find my own post in the forum listings... only through my recent activity... and if I cannot find it already...
[:o]
EDIT: nevermind, it showed up, took awhile though
PJ
And now I have a headache... what an absolutely roundabout way of posting a new forum topic..
Also I cannot seem to find my own post in the forum listings... only through my recent activity... and if I cannot find it already...
[:o]
EDIT: nevermind, it showed up, took awhile though
PJ
Posted by:
786_ak
12 years ago
I have the same situation as the pjgeutjens. And no one seems to be answering that 911 calls on this.
AK
AK
Posted by:
pjgeutjens
12 years ago
no one seems to be answering that 911 calls on this
Go have a look on Symantec connect, in the Wise Packaging forum. I actually got a very nice reply from Ed Tippelt on my question there.
If anyone here still would like to share their insights, feel free
PJ
Posted by:
786_ak
12 years ago
Actually, I just did, thanks. So using InstallScript wouldn't really fully serve the purpose, right?
Thanks
AK
Thanks
AK
Posted by:
Arminius
12 years ago
If you don't mind using a 3rd party tool, WinBatch is a pretty good scripting tool. it's got a lot of functions built in that do in one line what VB needs to have coded, especially if you want it to return success/failure. the biggest disadvantage to it is that there isn't a tenth of the online information that VBScript has.
Posted by:
kardock
12 years ago
winbatch is a very good scripting tool alright. the downside of it is that you need a dll file to run your EXEs.
we had to get rid of winbatch because when distributing a package via sccm, sometimes the dll was not extracted from the EXE, which has failed a few installations.
in other words, make sure to test it thoroughly.
we had to get rid of winbatch because when distributing a package via sccm, sometimes the dll was not extracted from the EXE, which has failed a few installations.
in other words, make sure to test it thoroughly.
Posted by:
pjgeutjens
12 years ago
Actually, I just did, thanks. So using InstallScript wouldn't really fully serve the purpose, right?
The biggest issue with InstallScript, and to a lesser extent WinBatch as stated above, is that you need a client side component installed (ISScript.msi or the WinBatch dll) in order to run the code. This adds a level of complexity that I'd rather avoid.
For now I've advised sticking to WiseScript, since we have some Wise licenses anyway, and keeping an eye out for Symantec Installshield. I might look into setting up a vbs function library that would allow 'low-treshold' coding for the wrappers, but that will be more of a side-project. It would also mean either giving up or looking for a way to wrap up .exe install scripts though..
Kr,
PJ
Posted by:
kardock
12 years ago
i should have added that here, we have dropped wisescript for vbscript, and powershell is considered to replace vbscript as soon as everyone had the training.
our VBS scripts are top notch, do the job and do not need a client side component.
our VBS scripts are top notch, do the job and do not need a client side component.
Posted by:
blacklisted_packager
12 years ago
Another viable alternative since you already were making wrappers in NSI script. This is a freeware and can be used for everything which Wise Script Does. Very easy to learn and quiet robus.Gives a direct exe without any requirement of a pre-req. You can visit the site http://nsis.sourceforge.net/Main_Page
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.