Run MSI through Conflicts, ignore GUIDs

[CChong]

We have several MSIs that were originally ran through conflicts. Many of the conflicts were resolved by synching the GUID of the conflicting components.

If you re-run an MSI, it no longer reports any conflicts because the GUIDs are synched. Is there a way to re-run an MSI but ignore the GUID -- in other words, have it report the conflict, even though the GUIDs are the same?

Thanks!

[CChong]

Since it seems that no one has any ideas on this, how about a way to quickly change the GUID on ALL components in an MSI?

[CChong]

A number of the ACEs include CARDs that resolve by syncing the Component - ComponentId (i.e. a GUID) column. If you want to do conflict checking without consideration of any component attributes, then you have two choices.

The first choice is to wait for the soon to be released AdminStudio v5.5 which includes a reconfigured ACE23 and ACE24 to do general purpose file and registry conflict checks.

The second choice is to use the Rules View / Rules Wizard from the ConflictSolver - Conflict menu to create custom rules. These custom rules can be created in a variety of forms including a native C++ SDK form to allow full end user control over the behavior of the ACE detection process.

Allen Saxton
InstallShield AdminStudio Development