Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0, Справочник

Страница: 93 / 302

Wise Package Studio Reference 93
Wise Package Studio Tools
Specifying OS Compatibility for Isolation
¾
Not available in Standard Edition.
In Application Isolation, the Select OS Compatibility page appears only if you chose to
use manifests as the Isolation Method. Complete the page as follows:
To specify OS compatibility for isolation
1. Mark the operating system(s) to support:
„
Support prior operating systems also
Because manifests are a .NET technology that work only on Windows XP or
later, an installation using manifests will not run on any other operating system.
This option lets you work around this limitation by configuring the installation so
that it is compatible with any operating system. It creates an installation file
with two copies of your installation. One is run if the operating system is
Windows XP or later with isolation taking place using manifests. The other is run
on all other operating systems with no isolation. This option significantly
increases the size of the installation.
„
Support Windows XP or later only
This option creates an installation that runs only on Windows XP or later and
uses manifests for isolation.
2. Mark the assembly type:
„
Create private side-by-side assemblies in application directory
Files and manifests, which together form assemblies, are installed to the
application directory if they are isolated.
„
Create shared side-by-side assemblies in WinSxS directory
Isolated assemblies are stored in the WinSxS directory, a global directory in the
Windows directory for the side-by-side isolation of files. It provides a shared
location, yet manages the isolation of files by comparing the digital signatures
of files to determine differences. Files in the WinSxS directory must be digitally
signed.
3. To also install the isolated files in their original location, such as System32, mark
Place copy of isolated files in their original location for application not
written to support isolation.
This prevents the application from breaking in the event that the application you are
isolating does not support isolation. Example: If it uses hard coded paths to access
support files.
4. From Extracted Files Directory, select a directory for the isolated files.
Isolated files are extracted and saved in this directory. When the installation is
subsequently saved and compiled, these files are pulled from the new directory, not
the original directory
.