Execution Order Of Multiple Merge Modules - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

sjeslis
Posts: 308
Joined: Mon Aug 22, 2011 11:40 pm
Contact: Website

Execution Order Of Multiple Merge Modules

Perhaps this is a Windows Installer architecture question but I'd thought I'd ask since I will need to know the answer of this very soon.

We have a master MSI install suite that will load up to three merge modules. I think at least two of these might have dependencies on each other (e.g. one assumes an XML config file was installed before hand, i.e. by another merge module).

What's the actual order of execution, if any, of multiple merge modules in an MSI? Is this order "predictable"?

Scott J.
Scott Jeslis
Senior Software Engineer
Cicero, Inc.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Execution Order Of Multiple Merge Modules

Hello Scott,

Please keep in mind that merge modules added to an installation project will be embedded in the installation package and they will not be installed as separate packages. The project to which you add a merge module and the module itself are merged at build time. Therefore, after the package is built the merge module is not a separate element anymore. So, there is no execution order for merge modules.

Also, when you add a merge module to your project, the merge module components will be added to a project installation feature (by default it is the Main Feature). So, if your merge modules have dependencies on each other you should add them to the same feature.

If you have any questions let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”