Any Better Alternative for Merge Module ?
I n Our Organisation we are having problem with the packages which are using Merge Modules instead of adding the dlls or ocx files directly into the package.
Installshield is adding merge modules which are using older version files than the app owner provided versions. When we install the package on the machine, package will install the dlls or ocx if the existing file versions is less than the merge module has. Since the merge modules we are adding in the package are having older version dlls than app owner provided. To fix this issue in our packages, We had to remove the merge modules and add files directly into the package.
I am wondering anyone has any better alternative to doing this ?
Answers (3)
Presumably you have been using merge modules (MMs) because they contain the file-set which best fits with your build. It sounds like you have allowed - for probably good reason - a number of applications to "violate" the build integrity by updating certain files. So, perhaps it's time to update your build or the MMs? This will involve obviously extensive testing of your core applications.
Alternatively, have you considered either side-by-side installation or the ".local" approach?
I would avoid using merge modules unless you have the time and resources to create and maintain your own library.
Instead, if you use a tool which allows conflict management, ensure that key DLLs such as you would find in merge modules all share the same GUID - that's basically what happens in merge modules. As a secondary consideration, you could mark the DLL components as "permanent" so you do not encounter any reference counting issues if the GUIDs are not all the same.