Hello everybody. [:D]

I am doing a kind of package that is almost a miracle to the costumer hehe.

I will try to explain. I am trying to put another msi to execute with my principal msi using nested msis, i am doing a dialog "user interface" dialogs to the costumer set some configurations to apply in this second msi. This first one will have all the dialogs to the user set some configuration (this configurations will be in some propertys, than in the end of this installation i will pass all this configurations that were in the property to the second msi. I try many things to do it, but without success. When i will install this package, first show me the dialog to set the configurations, than need to apply this configurations in the second msi using property settings, but the package is installing first the second msi and than in the end set the property. I already set the custon action "nested msi on source location" to execute in the installfinilize. but without success.

Well i hope this explain everything. Please can somebody help me [:(] with any ideas to fix this, or create something new.

Thanks a lot
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


Nested MSIs are to be actively discouraged, as there will be issues with patches and upgrades on the "child" MSI.

If all you need is to glean information from the user, why not add a dialog to collect that and store it in a transform? That transform can then be applied to the MSI from the command line.
Answered 09/14/2009 by: VBScab
Red Belt

Please log in to comment
Hi Eduardo,
your approach looks pretty strange to me.
You are collecting information in the first MSI and store them in properties.
Then reach them to the second one. This is an overkill.
Things like that are possible with one single MSI!
What exactly does not work, if you do it in one single MSI?
Which SW are you using to produce your MSI files?
Regards, Nick
Answered 09/14/2009 by: nheim
Tenth Degree Black Belt

Please log in to comment
Hello everyone, thanks a lot to help, i made like this:

1 - i set some installshield dialogs to recive a specific value that the costumer wil set.
2 - this values i stored in some propertys.
3 - than i set a custon action (nested msi on source location) and i pass to him all the properties.
4 - in the second msi i set all the conditions and registries that will recive the values that the costumer set in the first msi.

when the package start the installation, the first thing that will call is the installshield dialog, than will set all the steps that i wrote in this reply.

that is this...
Thanks a lot for everything. [:D]
Answered 09/22/2009 by: Edu_Tonin
Yellow Belt

Please log in to comment
Wouldn't it be simpler to copy the dialog from the first MSI to the second?
Answered 09/23/2009 by: VBScab
Red Belt

Please log in to comment