Hi I’m using a Chained.msi to install 2 other msi’s. New installs and uninstalling is work but it is not doing the small minor upgrades. The condition for the. What Chained MSI packages have been possible for a several years now ever since Windows Installer 4.5. Starting with InstallShield 2009 packagers have the option to.
By David Cole, Senior Software Engineer, IBM Introduction Install developers often need to include other products within their own setup. Sql Express Version 655. Flexera Software’s InstallShield 2009, coupled with Microsoft’s Windows Installer (MSI) 4.5, offers new options for chaining installs together while avoiding the problems associated with the existing options of merge modules and nested installs.
This white paper describes using chained. Bomberman 94 Pc more. msi packages in InstallShield 2009 and MSI 4.5 to componentize a setup. You will learn how to include other.msi packages within your own so that the result may be installed with the appearance of being a single product. The white paper also compares chained.msi packages with InstallShield prerequisites, which provide another method for including third-party setups. Footnotes are added with links to the InstallShield and MSI help for additional details.
The problem with merge modules Microsoft originally developed merge modules as the preferred method within MSI for developing components to be shared among multiple products. A key problem with merge modules, however, is that the contents of a merge module are installed under the ProductCode1 of the product that includes the merge module. Consequently, merge modules cannot be serviced independently; any service update for the merge module must be packaged as a service update to the containing product.
For example, suppose a version of Acme WidgetWorks included Microsoft’s Windows Scripting Host 1.0 merge module, and that Microsoft later released a service update for that merge module. Acme WidgetWorks would then have to release a service update of its own that includes the Microsoft update. This can quickly become a service nightmare, especially if there are urgent security issues involved. The problem with nested installs MSI has always had the restriction that only one MSI install can make system changes at a time. This locking mechanism helps ensure system integrity, but also limits where and how nested installations (sometimes called concurrent installations) can be run.
Microsoft acknowledged the need for one setup to be launched from within another and developed special custom action types for nested installations2. Microsoft has since deprecated these types of custom actions and discourages their use3, citing that, “they are difficult for customers to service.” A new hope: chained.msi packages Chained.msi packages is a new feature of MSI 4.5 and is supported by InstallShield 2009. This function allows individual.msi packages to be integrated into a containing, parent.msi setup so that the combined install is managed as a single transaction. Thus, if the install of one.msi package fails, then the entire install is rolled back.