Table of Contents
Advertisement
Process for Resolving Conflicts
ConflictManager Reference
See
Conflict Resolution Rules
Import packages into the Software Manager database, using Software Manager.
See Package Import in the Software Manager Help.
Note
Conflict detection requires package resources to be in the Software Manager
database. If a package's meta data is in the database but not its resources, you
must perform an import in Software Manager.
Typically, you will follow the steps below in the order listed. In some cases, however, you
might not follow all these steps. Example: During the analysis phase of a repackaging
project, you might want to check for conflicts but not resolve them. In that case, you
would perform the conflict detection step only.
1.
Detect conflicts.
ConflictManager compares the resources each package installs. When it finds
resources that conflict, it populates the Software Manager database with conflict
information.
View conflicts in the Applications/Packages pane and the Conflict List, or use the
ConflictManager reports to display and print conflict information.
See
Detecting Conflicts
2.
Resolve conflicts.
Resolving a conflict involves looking at each file that is installed by multiple
packages and selecting the version to install on the destination computer. You also
can change the location of conflicting files so that each package can use its version
of the file.
You can use conflict resolution rules to resolve conflicts automatically, or run the
Resolve wizard, which lets you review and resolve file conflicts one at a time.
See
Conflict Resolution
3.
Export resolved packages.
After you resolve conflicts, export the changes to the original Windows Installer or
WiseScript installation to produce an installation that does not conflict with other
packages.
See
Package Export After Conflict Resolution
4.
Test the resolved installation.
After you save and recompile a resolved package, install it on a clean machine and
test it.
Note
It is important to test the package on a clean machine. A machine that is not clean
might contain newer versions of some of the files you resolved. Because these
newer files are not overwritten during the installation, you do not get a true
representation of the resolved installation.
5.
Redo conflict resolution if necessary.
on page 24.
on page 30 and
Viewing Conflicts
on page 35.
on page 45.
Conflict Detection and Resolution
on page 31.
29
Advertisement
Table of Contents
