Isolating Files - Symantec CONFLICTMANAGER 8.0 - REFERENCE V1.0 Reference

Table of Contents

Advertisement

Method
Aggressive
Isolation method
Isolated components
Application paths
(AppPaths)
ConflictManager Reference
How to copy with the
Resolve wizard
Use the Copy Down button

Isolating Files

Isolating files to resolve conflicts is generally safer than copying them.
When to isolate files
When different packages install the same executable file (.dll, .ocx, or .exe) to the
System directory or to any common directory.
When different packages install files having the same name but different values in
the Company field, meaning they were created by different manufacturers.
Isolation works by moving one or both of the files to their respective application
directories and telling the operating system to look for the file in the application
directory before looking in the System directory.
Note
When you isolate a file, the file is still copied to the System directory in addition to the
application directory. If the System directory already contains an earlier version of the
file, the earlier version is replaced. This could cause a problem in any package that uses
the earlier version of the file. Therefore, it is best to isolate both versions of the file in
their respective packages.
File isolation methods
How it works
Isolate files using Windows Installer
isolated components. The isolation is
managed by the operating system.
Moves files out of the System
directory and into a private
directory, typically the application
directory.
When the conflicting files are listed in the registry, using an application path to move
them to a private application directory can cause problems. ConflictManager updates the
Conflict Detection and Resolution
How to copy with rules
Use a conflict resolution rule containing this
action:
Replace the conflicting files with the active
application's file
Add a condition to compare the package file
version to the conflicting files.
When to use
For .MSI and .WSI packages only
Whether or not conflicting files are listed
in the registry
For Windows Installer and WiseScript
packages
For installations intended for any Windows
operating system
When conflicting files are not listed in the
registry
(No programs will try to find it by looking
in the registry.)
38

Advertisement

Table of Contents
loading

This manual is also suitable for:

Conflictmanager

Table of Contents