10-21-2002, 08:37 AM
I got a bunch of merge modules and a bunch of MSI's. I want to check each MSI one at a time against the Merge modules for conflicts, how is this done. I can check two MSI's against each other no problem, so I tried putting all the merge modules into one MSI and running ConflictSolver on my merge module MSI and another MSI but it doesn’t pick up on conflicts I put in purposely to test this.
10-22-2002, 05:41 PM
As of AdminStudio release 3.5, there are two ACE rules related to Merge Modules.
ACE09 (http://www.installshield.com/isas/aces/ace09.htm) makes sure that if two packages contain merge modules with identical GUID, the MMs are really same (having same ModuleID and version). In other words, if merge modules with identical GUIDs have different ModuleId or version, ACE09 fails
ACE12 (http://www.installshield.com/isas/aces/ace12.htm) checks for files in the MSI package that can be replaced by Merge Module. In other words, if a same file (same name and version) is found in source MSI package and a merge module, ACE12 fails with a message that file should be replaced with a merge module.
Be sure to import merge modules into ConflictSolver database for above to work.
If you want to check for registry/shortcut/ini file, etc. conflicts between MSI and MSM, I think what you are doing (adding MSMs into a single MSI, which essentially populates File, Registry, Shortcut, etc. tables in MSI), should work.
I created a Merge Module with a shortcut, added this merge module to Package1.MSI, created Package2.MSI with same shortcut, and ACE13 (http://www.installshield.com/isas/aces/ACE13.htm) was raised in ConflictSolver.
I would recommend referring to ACE Reference (http://www.installshield.com/isas/aces/ACEReference.htm), as it sometime gets tricky when ACEs check for various things such as Component GUIDs, destination directories, etc.
If it still does not work, please email me (firstname.lastname@example.org) the MSI and MSM files, and I'll try to reproduce it here.
10-23-2002, 02:06 AM
Thanks for the help,
I was using an older version of AdminStudio, Ill download the 3.5 trial and give that a try.
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.