Table of Contents
Advertisement
Chapter 8: Converting Legacy Installations Using the Repackager Interface
Isolating Windows Installer Packages
Task:
To save the current Repackager project under a different name:
Select Save As from the File menu.
Opening InstallShield Editor from Repackager
After building your Repackager project into a Windows Installer package and/or an InstallShield Editor project, you
may want to launch InstallShield Editor for additional modifications.
Task:
To launch the generated InstallShield Editor project (.ism) in InstallShield Editor:
From the Repackager Project menu, select Edit InstallShield Project. If installed, InstallShield Editor opens the
project file.
Task:
To launch the generated Windows Installer package (.msi) in InstallShield Editor:
From the Repackager Project menu, select Edit Windows Installer Package. If installed, InstallShield Editor
opens the package in Direct MSI Edit mode.
Isolating Windows Installer Packages
Application isolation is one solution to component versioning conflicts. 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.
When building a Windows Installer package from your Repackager project, you can also choose to create an
isolated version of that package by selecting an option on the Repackaged Output View.
Information about application isolation is presented in the following topics:
•
About Application Isolation
•
About Assemblies
•
About Manifests
•
About Digital Certificates
•
Setting Isolation Options
•
Building an Isolated Windows Installer Package
546
ADS-0950-UG00
AdminStudio 9.5 User Guide
Advertisement
Table of Contents
Troubleshooting
