Symantec WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0 Reference page 91

Wise Package Studio Reference
Installation Pathname
Specify an installation in which to isolate .EXE files and click Next. You can
specify an .MSI, an .MST, an .MSM, a .WSI, or a .WSM.
If you specify an .MST, you can choose the same .MST in Updated Windows
Installer File on the Isolation Complete page to append the results of the
application isolation to that .MST, rather than overwriting it.
Base MST file
Specify a transform to apply to the installation.
3. On the Welcome page, mark your isolation method:
Use manifests to isolate application files
Adds .MANIFEST files to your installation. Manifests, a .NET technology, use
metadata to describe in detail the relationships between an .EXE and its .DLL
and .OCX files. You can specify that some support files are accessed from the
application directory and some are not. This method of isolation only works
when the installation is installed on a computer using Windows XP or later.
Use Windows Installer Isolated Components to isolate application files
This method of isolation offers less flexibility than manifests, but runs on more
operating systems. Support files are placed in the application directory along
with a .LOCAL file, which informs the operating system to access the .EXE's
support files from the application directory.
4. On the Welcome page, mark your isolation type:
Automatically isolate application files
This option automatically isolates all applications with all support files in the
installation. Example: Suppose your installation contains Sample1.EXE,
Sample2.EXE, and Sample3.EXE, and also contains four .DLLs stored in the
System32 directory. All four .DLLs will be copied to the application directory,
and if any of the three .EXEs call any of the .DLLs, the system will direct the
.EXEs to the isolated copies of the .DLLs in the application directory instead of
the ones in the System32 directory.
Manually choose which files to isolate with which applications
If you mark this, an additional page appears that lets you manually choose
which support files to isolate with which .EXE files. Example: If you isolate
Sample1.EXE with a specific version of the file comctrl32.DLL, then a copy of
comctrl32.dll will be isolated in the application directory along with
Sample1.EXE. When Sample1.EXE calls comctrl32.dll, the system will direct it to
the isolated copy.
5. On the Welcome page, click Next.
6. If you chose manifests, the Select OS Compatibility page appears.
a. Mark options for Operating System Support and Side-by-Side Assembly Type.
b. To have a copy of the isolated files installed in their original location, mark that
option.
c. Specify the extracted files directory.
See Specifying OS Compatibility for Isolation
7. If you chose Windows Installer isolated components, the Select Isolation Options
page appears.
a. Mark whether files should be moved to enable more comprehensive isolation.
Wise Package Studio Tools
on page 93.
91