Beruflich Dokumente
Kultur Dokumente
Directions
Application Isolation is the process which ensures that the packages that we create won't interfere with
each other by scanning them to determine if they are using only local resources and DLLs. Isolating an
application with its support files ensures that your application always uses the version of shared files with
which it was installed.
Why isolate an application?
1. Application isolation is one solution to component versioning conflicts, or DLL hell.
2. Isolation reduces versioning conflicts by modifying an application so it always loads the versions
of components such as DLLs with which it was originally developed and tested.
3. Application isolation provides increased stability and reliability for applications because they are
unaffected by changes caused by installation and ongoing maintenance of other applications on
the system.
4. Resolve incompatibilities between different versions of shared components.
5. Reduce the complexity of the installation by storing COM activation data in a manifest instead of
the registry.
6. Insulate the application from changes to shared components.
How to isolate an application.
Application isolation can be performed using one of these two methods.
folder as the application. This reduces the chance of errors after isolation resulting from how the
application was written.
The Application Isolation wizard in Wise Package Studio provides a quick and easy way to isolate
applications with their shared .DLL or .OCX files (support files).
The below steps describe how to implement the process using WPS.
1. Invoke the Application Isolation wizard from the side pane of Wise package studio as shown
below.
2.Browse the .WSI or .MSI file on which the isolation has to be performed.
3.Choose on the isolation method and the isolation type. The next screens depend on the options
selected here.
4. Choose how the process of isolation has to be taken place.
2.The updated Windows Installer file can be either the default MSI file appended with _isolated or a
new MSI file or a MST file, as shown here.