Symantec CONFLICTMANAGER 8.0 - REFERENCE V1.0 Reference page 15

ConflictManager Reference
Filter the conflict display.
The conflict display filter determines which packages and conflicts appear in the
Applications/Packages, Conflict List, and Conflict Details panes.
See Filtering the Conflict Display
Ignore conflicts when components are permanent.
When two Windows Installer applications install components with identical resources,
but different component GUIDs, ConflictManager detects a conflict. This happens
because Windows Installer installs and uninstalls resources at the component level.
Therefore, uninstalling one of the applications could result in the removal of one or more
of the resources required by the other application. However, when the components for
all such applications are marked to remain permanently installed, this conflict does not
occur. The permanent component remains installed even if all of the applications
associated with that component are uninstalled. ConflictManager does not consider such
cases to be conflicts.
Hide conflicts.
Conflicts that are identified by ConflictManager are often found to be harmless upon
further testing. To filter these harmless conflicts from the conflict display, you can
designate certain conflicts between specific packages to be ignored, or hidden.
To designate a conflict as hidden, (or to remove the "hidden" designation), click the
Application Name column and then right-click the conflict in the Conflict Details pane.
The Conflict Settings dialog box contains a check box, Display Conflicts Marked as
Hidden, that lets you show hidden conflicts.
See Hiding Conflicts on page 34.
Resolve Formatted Registry Values for Conflict Detection
Registry entries in Windows Installer and WiseScript packages can use formatted text
strings that, when evaluated literally, might lead to false positives during conflict
detection. To avoid this problem, Software Manager resolves the formatted text strings
during import of the following types of packages: .WSI, .MSI, .MSM, .MSP, .MST, .WSE.
Example: Application 1 creates a registry key under HKLM\Software\InstallDirKey with a
value of [$comp1]. Application 2 creates a registry key under
HKLM\Software\InstallDirKey with a value of [$comp4]. During installation, both
[$comp1] and [$comp4] evaluate to the same value. If these values were not resolved,
ConflictManager would identify this as a conflict. However, because Software Manager
resolves the values during import, and stores them in the Software Manager database, a
conflict is not detected, which is the correct behavior.
SoftwareManager resolves all properties in a Windows Installer installation. In a
WiseScript installation (.WSE), SoftwareManager resolves only the following predefined
variables:
WiseScript variable
%Common%
%fonts%
Introduction to ConflictManager
on page 33.
Resolves to
Program Files\Common
Windows\Fonts
15