/build/static/layout/Breadcrumb_cap_w.png

Merge Modules

Hi - don't worry - this is not another question asking what exactly merge modules are..

What I'd like to know is the best practice approach when faced with an app that installs files which are members of merge modules.

If an app installs a file to its own local installdir & this file is considered a member of a merge module what should be done.

- Should the file be removed and the appropriate merge module be placed in C:\windows \system32 ?
- Or are merge modules redirected to install to where the original file was installed?

I understand that the application exe should be able to find the appropriate file if I remove it from where it was originally installed but is this failsafe for all apps?
- Will the file be found where the merge modules default install location is?
- Do all merge modules default to C:\windows\system32

I generally use Installshield - when I manually include a merge module it defaults to the INSTALLDIR -
- Why this location?
- How will I know where it is 'suppossed' to go?

Any help will be much appreciated..

0 Comments   [ + ] Show comments

Answers (2)

Posted by: cranky1 14 years ago
Senior Yellow Belt
0
I have this same question (3 years after this person asked it). Can anyone respond to this? - Thanks!

"If an app installs a file to its own local installdir & this file is considered a member of a merge module what should be done.

- Should the file be removed and the appropriate merge module be placed in C:\windows \system32 ?
- Or are merge modules redirected to install to where the original file was installed? "
Posted by: cosmo_packager 14 years ago
Yellow Belt
0
Hello there

I think I have the answer to your problem. Merge modules are used to deliver shared code, files, resources, registry entries, and setup logic to applications as a single compound file.

When you have a merge module file in your INSTALLDIR you must check first the file version, if merge module has version equal or higher you can add the merge module and the file will be removed. You can see with file moon tool that main executable search the merge module in System Folder if isn’t near him in INSTALLDIR.

Almost all merge modules are installed to System Folder because this is the primary location for dll files. Using merge modules you can avoid many conflicts between different applications.

When you manually include a merge module it defaults to where is supposed to be installed not INSTALLDIR. You can open merge module file and see where will be installed.

Best regards.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ