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
- :
- InstallShield
- :
- InstallShield Forum
- :
- Prerequisites vs. Redistributables
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
‎Sep 26, 2014
10:07 AM
Prerequisites vs. Redistributables
Could someone please explain the difference between setting a prerequisite and adding a re-distributable such as a merge module?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 26, 2014
12:55 PM
Redistributabes are 3rd party pieces of technology that you can freely distribute with your software. Prerequisites and Merge modules are both different types of redistributables.
An InstallShield prerequisite is an installation for a product or technology framework that is required by your product.
A merge module (or .msm file) contains all of the logic and files needed to install distinct pieces of functionality. Unlike prerequisites, they cannot be run on their own, rather they are merged into the msi at build time.
I hope this helps.
An InstallShield prerequisite is an installation for a product or technology framework that is required by your product.
A merge module (or .msm file) contains all of the logic and files needed to install distinct pieces of functionality. Unlike prerequisites, they cannot be run on their own, rather they are merged into the msi at build time.
I hope this helps.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 29, 2014
07:39 AM
jlynch,
Thank you that clears up the confusion.
Thank you that clears up the confusion.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)