Hope this makes sense, I'm installing CorelDraw 11. This application requires an older version of ISScript. Is there a way to include the ISScript.msi into my CorelDraw11.msi? So that ISScript.msi is installed before CorelDraw11?

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
Hi Urban

Yes, there is a way to include a msi into another msi installation. It's called a 'nested installation'.
If this makes sense in your case (isscript.msi) is a political or even religious question as there are lots of people who don't deploy isscript at all but clean everything out of the original msi to prevent the need for isscript.
However, try this:

In CustomAction table add

Actions | Type| Source | Target |
-----------------------------------------------------------------------
Install_Isscript | 23 | isscript.msi | |
UnInstall_Isscript | 23 | isscript.msi | REMOVE="ALL" |

in InstallExecuteSequence table add

Actions | Condition | Sequence |
-----------------------------------------------------------------------
Install_Iscript | Not Installed | 6700 |
UnInstall_Isscript | REMOVE="ALL" | 1402 |

And be aware that the isscript.msi is in the same directory as your application msi

This worked fine for Adobe Reader with Update msi's.
However, there are few things to be aware of:
- you can only uninstall Isscript by uninstalling your application (because it is nested in it)
- if you uninstall your application, Isscript will be uninstalled as well (which may causes problems with other applications which may still need Isscript)

Do you use a deployment software where you could 'chain' the msi's? This would definitely be the better choice in this case.

I've heard that in Windows Installer 4 will be the functionality of chaining...

Hope that helps

Roland
Answered 11/04/2005 by: rpfenninger
Second Degree Green Belt

Please log in to comment
0
Is there a way to include the ISScript.msi into my CorelDraw11.msi?

I think an easier & better way to do this is to include the engine as an MSM as provided from Install Shield (Macrovision) web site. Then all you have to do is tick-off the check-box in the Redist view and away you go.

http://www.installshield.com/downloads/modules.asp?prod=ISX&lan=english&xmlUse=y

look for:

InstallShield Scripting Engine InstallShieldScriptingEngine.msm 10.x 5/1/2004 2.39 MB
InstallShield Scripting Engine InstallShieldScriptingEngine.msm 10.01 7/28/2004 2.46 MB
InstallShield Scripting Engine InstallShieldScriptingEngine.msm 7.x KB Q107359 11/21/2002 1.7 MB
InstallShield Scripting Engine InstallShieldScriptingEngine.msm 9.x KB Q110580 11/21/2003 2.3MB
InstallShield Scripting Engine InstallShieldScriptingEngine.msm 8.x KB Q107463 11/21/2002 1.7 MB

They have a 10.5 version around somewhere I think .... but as you all are painfully aware, Macrovision does not believe in effective search engines for it's own site. Try google.

Regards, William
Answered 11/04/2005 by: williamp
Orange Belt

Please log in to comment
0
ORIGINAL: rpfenninger

Hi Urban

Yes, there is a way to include a msi into another msi installation. It's called a 'nested installation'.
If this makes sense in your case (isscript.msi) is a political or even religious question as there are lots of people who don't deploy isscript at all but clean everything out of the original msi to prevent the need for isscript.
However, try this:

In CustomAction table add

Actions | Type| Source | Target |
-----------------------------------------------------------------------
Install_Isscript | 23 | isscript.msi | |
UnInstall_Isscript | 23 | isscript.msi | REMOVE="ALL" |

in InstallExecuteSequence table add

Actions | Condition | Sequence |
-----------------------------------------------------------------------
Install_Iscript | Not Installed | 6700 |
UnInstall_Isscript | REMOVE="ALL" | 1402 |

And be aware that the isscript.msi is in the same directory as your application msi

This worked fine for Adobe Reader with Update msi's.
However, there are few things to be aware of:
- you can only uninstall Isscript by uninstalling your application (because it is nested in it)
- if you uninstall your application, Isscript will be uninstalled as well (which may causes problems with other applications which may still need Isscript)

Do you use a deployment software where you could 'chain' the msi's? This would definitely be the better choice in this case.

I've heard that in Windows Installer 4 will be the functionality of chaining...

Hope that helps

Roland



Hello, should these number have to be the same on everything nested MSI? Or they have to be between specific action?

Thanks!
Answered 02/08/2006 by: wd40
Orange Senior Belt

Please log in to comment
0
Think I got it.

Thanks to an old job friend.

First of all, created a blank MSI with WIWW.

Then I integrated all the ISSScript that use the same GUID.

Added some custom action and InstallExecuteSequence and the trick is done.

Now my problem is about uninstallation... need to find something :)
Answered 02/09/2006 by: wd40
Orange Senior Belt

Please log in to comment
0
Hi
I am installing Rational Robot(msi).While installing this msi ,I get a message box prompting me to run ISScript.msi prior to this installation.
ISScript is available as isscript1050.msi

So i tried the following

In CustomAction table add

Actions | Type| Source | Target |
-----------------------------------------------------------------------
Install_ISScript | 23 | isscript1050.msi | |
UnInstall_ISScript | 23 | isscript1050.msi | REMOVE="ALL" |

in InstallExecuteSequence table add

Actions | Condition | Sequence |
-----------------------------------------------------------------------
Install_ISScript | Not Installed | 6700 |
UnInstall_ISScript | REMOVE="ALL" | 1402 |

BUT STILL I AM GETTING THE SAME MESSAGE BOX .
Want to know if the rows added r incorrect..

Pls help..
Answered 10/24/2007 by: ycanti
Senior Yellow Belt

Please log in to comment
0
Hi ycanti,
IMHO, this can't work at all! You try to install the ISscript engine at the very end of the install. What should that be good for?
An MSI which uses the engine, calls it very early, right after the install begins. So, the only solution is, to install it as one of the first actions.
See this post for a deeper explanation: http://itninja.com/question/msi-corporate-standardiser6
Hope, this point you in the right direction.
Regards, Nick
Answered 10/24/2007 by: nheim
Tenth Degree Black Belt

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