Replies: 1 comment
-
It's not clear to me where your UI/UX is. Is it in the bootstrapper or are you running your MSIs with Native MSI UI? If the former, this is a great place to collect the data and pass it to both MSIs. If it's the latter, that's kind of a bad experience because you no longer have one continuous transaction. There is no way for an MSI to return anything back up to the bootstrapper except for an exit code. The only thing that I can think of is have MSI 1 record the values to the registry and have MSI 2 read those values and use them instead of the default. It also feels like a bit of a component rule violation. Perhaps MSI 2 shouldn't be concerned about these values at all and that product 2 should just detect the settings from product 1 through some agreed API even if it is just a common registry location. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
There is a bundle file where there is a chaining of multiple msi file and based on install conditions two or more msi packages will be installed. There are property defined in all the product.wxs files and they have some default value. The default values can be overwritten/modified during the installation by the user. The updated value is needed to be passed to the next msi in the chain, how can this sharing of values be achieved?
Beta Was this translation helpful? Give feedback.
All reactions