Does anyone know if it is possible to create a chained package with LE? I can create an installation msi with my project (C#) however I need to embed the MSSQL LocalDB installation with my project. Creating a chained.msi package with InstallShield 2009 is very easy; simply navigate to the Releases view, right-click on ‘Chained.msi packages’ in the center panel and select ‘New Chained Package’. Install developers often need to include other products within t heir own setup. Flexera Software’ s InstallShield 2009, coupled with Microsoft’ s Windows Installer (MSI) 4.5, offers new opt ions for chaining installs together while avoiding t he problems associated with the existing options of merge modules and nested installs. This white paper describes using chained.msi packages in InstallShield 2009 and MSI 4.5 to componentize a setup. You will learn how to include ot her.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 provi de anot her method for including third-party setups. Footnote s are added with links to t he InstallShield and MSI help for additional details. Of the product that includes the merge module. Conseque nt ly, merge modules cannot be serviced independently; any service update for t he merge module must be packaged as a service update to t he containing product. For example, suppose a version of Acme WidgetWorks included Microsoft’ s Windows Scripting Host 1.0 merge module, and t hat Microsoft later released a service update for t hat merge module. Acme WidgetW orks would t hen have to release a service update of its own t hat includes t he Microsoft update. T his can quickly become a service nightmare, especi ally if t here are urgent security issues involved. Chained.msi packages is a new feature of MSI 4.5 and is supported by InstallShield 2009. This funct ion allows individual.msi packages to be integrated into a containing, parent.msi setup so that t he combined install is mana ged as a single transaction. Thus, if t he install of one.msi package fails, then the entire install is rolled back. When the parent product is uninstalled, the chained.msi package s are also uninstalled (although there are other options available). Perhap s most important ly, each const ituent.msi package is installed under its own ProductCode. This means t hat each product can be serviced indepe ndently and t hus avoids one of t he major problem s wit h merge modules. MSI 4.5 uses the chained.msi package’s own ProductCode to determine whether t hat package has alrea dy been installed or not, and thus skips the install step for packages that have already been installed. Similarly, if a chained.msi package has been upgraded so that it now has a different Prod uctCode, or if the package has already been uninstalled, then the uninstall step for that package is skipped in t he parent uninstall. Thus, chained.msi package s behave as you would generally desire without having to write additional code. We’ll discuss prerequisites in greater detail later in t his white paper. Ct dmv drivers license renewal. MSI 4.5 is only required for t he parent.msi package. Child packages are not require d to use any part icular version of MSI. Installing MSI 4.5 does requir e a reboot, although t he symptoms vary based on the version of Windows being used. On Windows XP and Windows Se rver 2003, t he reboot is automatically deferred to the end of the setup. That is, on these versions of Windows a setup that installs MSI 4.5 will run to completion and t he user will be prompted for a reboot when t he setup completes. On Windows Vista, a reboot is require d immedia tely after MSI 4.5 is installed. Based on discussions in t he InstallShield 2009 Communi ty.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |