Resolving File Conflicts Within Windows Installer Editor; Resolving Conflicts With Rules In Windows Installer Editor - Symantec WINDOWS INSTALLER EDITOR 8.0 Reference

Hide thumbs Also See for WINDOWS INSTALLER EDITOR 8.0:
Table of Contents

Advertisement

Resolving File Conflicts Within Windows Installer
Editor

Resolving Conflicts With Rules in Windows Installer Editor

Windows Installer Editor Reference
Not available in Standard Edition.
You can detect and resolve conflicts between a package that is still in the authoring
phase and those that have already been deployed, without importing the package into
the Software Manager database. The best time to do this is as you add files to an
installation. This lets you:
Streamline repackaging by identifying conflicts earlier in the process.
Maintain your Software Manager database as a pristine image of packages that have
already been deployed in the production environment.
Example:
Suppose you are working on an update to Application A, which is scheduled for a future
release. You import Application A into the Software Manager database to resolve
conflicts. Another member of your team is working on Application B, which uses older
versions of some of the files in Application A. When you import Application B into the
Software Manager database, these files conflicts are found and resolved by pulling in the
newer versions from Application A. You release Application B with files from Application
A that have not been released. You can avoid this situation by resolving conflicts without
importing into the Software Manager database.
How Windows Installer Editor detects conflicts
Windows Installer Editor compares the files each application installs and records files
that conflict. Resolving a conflict involves looking at each file that is installed by more
than one package and selecting which 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. When you resolve conflicts from Windows Installer Editor, all conflicts
are resolved in the current installation only; the Software Manager database is never
changed.
Options for resolving conflicts
Resolve Conflicts with Rules
Uses ConflictManager's conflict resolution rules to resolve conflicts automatically.
See
Resolving Conflicts With Rules in Windows Installer
Resolve Conflicts
Runs the Resolve wizard, which lets you review and resolve file conflicts one at a
time.
See
Resolving Conflicts Individually in Windows Installer Editor
Not available in Standard Edition.
Using conflict resolution rules is the fastest way to resolve conflicts. The rules do the
conflict analysis and resolve the conflicts automatically. This saves time, reduces errors,
and provides consistency in conflict resolution.
See Conflict Resolution Rules in the ConflictManager Help.
Assembling an Installation
Editor.
on page 136.
135

Advertisement

Table of Contents
loading

Table of Contents