As I understand it, MSIs which include Isscript can be coverted in InstallShield Pro to a 'normal' MSI, ie no dependency on the isscript engine.

Since deploying the multiple versions of Isscript can be a pain, what's the point? Why are MSIs distributed in this dependent format? Is functionality lost when MSIs are converted?

Thanks
0 Comments   [ + ] Show Comments

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.

Answers

0
In some cases the ISScript does do something useful such as install a driver or pass parameters to MSIEXEC when doing an upgrade. It really depends on how the setup was authored. For the most part you can do away with it without much consequence but always be aware that sometime you will need to run that Setup.exe for everything to work.
Answered 01/09/2006 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity