This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Merge Module
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 15, 2010
08:38 AM
Merge Module
I need to add some merge module to work my application.
How can I add merge module with my windows Installer product?
How can I add merge module with my windows Installer product?
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 15, 2010
09:31 AM
Merge Modules
InstallAnywhere 2010
Merge Modules are essentially installer sub-projects that can be created independently of one another and later merged together. Like an installer, a Merge Module is a reusable collection of installation functionality, complete with features, components, panels, actions, and files.
However, a Merge Module cannot be installed on its own; instead, developers use Merge Modules when they want to include the functionality of one installer within another installer.
• Benefits of Using Merge Modules
• Using Third Party Merge Modules
• Methods to Add Merge Modules to an Existing Installer
• Integrating Merge Modules Into Projects
Benefits of Using Merge Modules
Merge Modules provide many benefits and provide solutions to complex installation requirements. For instance:
Benefits of Using Merge Moduels
Benefit
Description
Can Use to Create a Suite Installer
Combine several Merge Modules from different products to create a “Suite Installer.”
Can Be Used by Independent Development Teams
Independent development teams in different locations can create Merge Modules for different software components. A release engineer can combine those Merge Modules into a single product installer.
Self-Contained Units Can Be Reused in Future Installer Projects
Create self-contained units of installer functionality for reuse in future installer projects. For instance, if the same software component needs to be in several different installers, build it into a Merge Module and make it available for all of the installer developers.
Enables You to Store Common Installer Functionality
Save common installer functionality, such as License Agreement panels and Custom User Input panels, into Merge Modules to simplify future installer project creation.
Can Combine With Third Party Software Packages
Combine Merge Modules from 3rd party software packages to build complex software “Solutions,” without having to figure out how to install each individual package.
Using Third Party Merge Modules
InstallAnywhere provides many third-party Merge Modules on its Web site.
• Use as a template—You can use a Merge Module as the starting point for a new installer project. These Merge Modules are referred to as Templates, and are covered in another section.
• Combine with installer projects—Any installer project can be built into a Merge Module. And any Merge Module can be used within any other installer project.
• Create during installer build process—Merge Modules are created as an option through the installer build process. Since a Merge Module contains all of the resources for a project, it is just like building an installer. They can be built automatically when the installer is built, or they can be explicitly built from the Advanced Designer (check the Build Merge Module option on the Build task, under the Distribution tab) or from the command line (use the +merge option).
Methods to Add Merge Modules to an Existing Installer
Merge Modules can be merged into an existing installer in one of three ways:
Methods to Add Merge Module to an Existing Installer
Method
Description
Import Dynamic Merge Module
In the Organization > Modules task, click Import Dynamic Merge Module to merge a Merge Module into the current installer.
• All of the Merge Module’s files, actions, and panels (optionally) will be combined into current project.
• The actions will appear as in an Action Group in Pre-Install and Post-install.
Dynamic Merge Modules are recommended if you have Merge Modules whose contents constantly change. A parent project will automatically refresh dynamic Merge Modules when the parent project is loaded and built.
Import Merge Module
In the Organization > Modules task, click Import Merge Module to merge a static Merge Module into the current installer.
• All of the Merge Module's features, components, files, actions, and panels (optionally) will be combined into the current project, allowing developers to further customize any settings.
• Static Merge Modules are recommended if you want import features and components and if you want more freedom in the place actions.
• Changes made to a static Merge Module will not be noted in the parent project.
Installed as Self-Contained Sub-Installer Units
Merge Modules can also be installed as self-contained sub-installer units, without merging them into the current project.
This is useful if developers do not know what will be in a Merge Module, or they will not be modifying any settings. Merge Modules added in this manner are run as silent sub-installers.
Integrating Merge Modules Into Projects
Merge modules can be integrated with a project in one of two ways:
Methods to Integrate Merge Modules Into Projects
Method
Description
Bundle Merge Module at Build Time
Use the Install Merge Module action and select Bundle Merge Module at Build Time, if the Merge Module is available when ready to build the installer. These Merge Modules will be included in the actual generated installer.
Locate Merge Module at Install Time
Use the Install Merge Module action and select Locate Merge Module at Install Time to have the installer install a Merge Module that is available at install time, but external to the installer. The Merge Module can be either on the end user's system or stored on a CD. If the location is a folder that contains several Merge Modules, they will all be installed.
See Also
Uninstaller for Merge Modules and Multiple Products
Distribution Subtab
Templates
InstallAnywhere 2010 Help Library
02/02/2010
Copyright Information | Contact Us
InstallAnywhere 2010
Merge Modules are essentially installer sub-projects that can be created independently of one another and later merged together. Like an installer, a Merge Module is a reusable collection of installation functionality, complete with features, components, panels, actions, and files.
However, a Merge Module cannot be installed on its own; instead, developers use Merge Modules when they want to include the functionality of one installer within another installer.
• Benefits of Using Merge Modules
• Using Third Party Merge Modules
• Methods to Add Merge Modules to an Existing Installer
• Integrating Merge Modules Into Projects
Benefits of Using Merge Modules
Merge Modules provide many benefits and provide solutions to complex installation requirements. For instance:
Benefits of Using Merge Moduels
Benefit
Description
Can Use to Create a Suite Installer
Combine several Merge Modules from different products to create a “Suite Installer.”
Can Be Used by Independent Development Teams
Independent development teams in different locations can create Merge Modules for different software components. A release engineer can combine those Merge Modules into a single product installer.
Self-Contained Units Can Be Reused in Future Installer Projects
Create self-contained units of installer functionality for reuse in future installer projects. For instance, if the same software component needs to be in several different installers, build it into a Merge Module and make it available for all of the installer developers.
Enables You to Store Common Installer Functionality
Save common installer functionality, such as License Agreement panels and Custom User Input panels, into Merge Modules to simplify future installer project creation.
Can Combine With Third Party Software Packages
Combine Merge Modules from 3rd party software packages to build complex software “Solutions,” without having to figure out how to install each individual package.
Using Third Party Merge Modules
InstallAnywhere provides many third-party Merge Modules on its Web site.
• Use as a template—You can use a Merge Module as the starting point for a new installer project. These Merge Modules are referred to as Templates, and are covered in another section.
• Combine with installer projects—Any installer project can be built into a Merge Module. And any Merge Module can be used within any other installer project.
• Create during installer build process—Merge Modules are created as an option through the installer build process. Since a Merge Module contains all of the resources for a project, it is just like building an installer. They can be built automatically when the installer is built, or they can be explicitly built from the Advanced Designer (check the Build Merge Module option on the Build task, under the Distribution tab) or from the command line (use the +merge option).
Methods to Add Merge Modules to an Existing Installer
Merge Modules can be merged into an existing installer in one of three ways:
Methods to Add Merge Module to an Existing Installer
Method
Description
Import Dynamic Merge Module
In the Organization > Modules task, click Import Dynamic Merge Module to merge a Merge Module into the current installer.
• All of the Merge Module’s files, actions, and panels (optionally) will be combined into current project.
• The actions will appear as in an Action Group in Pre-Install and Post-install.
Dynamic Merge Modules are recommended if you have Merge Modules whose contents constantly change. A parent project will automatically refresh dynamic Merge Modules when the parent project is loaded and built.
Import Merge Module
In the Organization > Modules task, click Import Merge Module to merge a static Merge Module into the current installer.
• All of the Merge Module's features, components, files, actions, and panels (optionally) will be combined into the current project, allowing developers to further customize any settings.
• Static Merge Modules are recommended if you want import features and components and if you want more freedom in the place actions.
• Changes made to a static Merge Module will not be noted in the parent project.
Installed as Self-Contained Sub-Installer Units
Merge Modules can also be installed as self-contained sub-installer units, without merging them into the current project.
This is useful if developers do not know what will be in a Merge Module, or they will not be modifying any settings. Merge Modules added in this manner are run as silent sub-installers.
Integrating Merge Modules Into Projects
Merge modules can be integrated with a project in one of two ways:
Methods to Integrate Merge Modules Into Projects
Method
Description
Bundle Merge Module at Build Time
Use the Install Merge Module action and select Bundle Merge Module at Build Time, if the Merge Module is available when ready to build the installer. These Merge Modules will be included in the actual generated installer.
Locate Merge Module at Install Time
Use the Install Merge Module action and select Locate Merge Module at Install Time to have the installer install a Merge Module that is available at install time, but external to the installer. The Merge Module can be either on the end user's system or stored on a CD. If the location is a folder that contains several Merge Modules, they will all be installed.
See Also
Uninstaller for Merge Modules and Multiple Products
Distribution Subtab
Templates
InstallAnywhere 2010 Help Library
02/02/2010
Copyright Information | Contact Us
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 16, 2010
12:37 AM
IA allows to add Merge Module template with .iam.zip extension.
I want to add some free merge module provided by MS like Microsoft_VC80_CRT_x86.msm & msxml4.msm.
My mergemodules are having .msm extension.
Please suggest.
TIA
I want to add some free merge module provided by MS like Microsoft_VC80_CRT_x86.msm & msxml4.msm.
My mergemodules are having .msm extension.
Please suggest.
TIA
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 16, 2010
12:42 AM
Hi,
IA only allows merge modules which are created with IA and it does not allow merge modules which are created with msm extension.
Thanks,
IA only allows merge modules which are created with IA and it does not allow merge modules which are created with msm extension.
Thanks,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 10, 2010
10:17 AM
Any of you know where on website I can find a listing/summary of the 3rd Party Merge Modules that InstallAnywhere provides? Looked for a listing in the documentation but it says go to the website...
Thanks 😛
Thanks 😛
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 11, 2010
12:59 AM
And have you gone to the website and you didn't find them?!? They're still where they used to be for years now:
http://www.flexerasoftware.com/products/installanywhere/files-utilities.htm
Just click on the Merge Modules tab!
http://www.flexerasoftware.com/products/installanywhere/files-utilities.htm
Just click on the Merge Modules tab!
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)