Repackaged Output View

AdminStudio 2021 | 21.0 | Repackager

Edition:This feature is available in AdminStudio Standard, Professional, and Enterprise Editions.

From this view, you can configure build options for the project, including whether to build an MSI package automatically following conversion.

The following properties are available for configuration:

Repackaged Output View Options

Option

Description

Editor Project

Provide the name and location of the InstallShield Editor project (.ism) file.

Windows Installer Package

The name and location of the Windows Installer package (.msi).

By default, Repackager creates the Windows Installer package in a subdirectory, named MSI_Package, of the directory containing the Repackager project file. To change this default location, you need to edit this Repackager project’s associated InstallShield Editor project file.

Note:If a Windows Installer package has not yet been built from this Repackager project, (not built) is listed.

Create Microsoft Windows Installer Package

If this option is selected, after creating the InstallShield Editor project file (.ism), a Windows Installer (.msi) file will also be built.

Windows Installer Package Options

If you have selected the Create Microsoft Windows Installer Package option, you need to also select one of the following options:

• Single Compressed .MSI File—Select this option if you want to compress all necessary files inside the .msi package, as opposed to storing them outside of the .msi database.
• Single Compressed Setup.exe File—Select this option if you want to compress all files inside a setup.exe file, including the .msi file and all other necessary files.
• .MSI File With External .CAB File—Select this option if you want to create an .msi file and want to compress the rest of the necessary files in an external .cab file.
• .MSI File With External .CAB File and Setup.exe—Select this option if you want to create an .msi file and a setup.exe file, and want to compress all the rest of the necessary files in an external .cab file.
• Uncompressed .MSI File—Select this option if you want to create an uncompressed .msi file. All of the rest of the necessary files, in uncompressed format, would be shipped with the .msi file.
• Uncompressed .MSI File With Setup.exe—Select this option if you want to create an uncompressed .msi file along with a setup.exe file. All of the rest of the necessary files, in uncompressed format, would be shipped with the .msi and setup.exe files.

Create Isolated Version of the Package

Select this option to create a second, isolated version of the Windows Installer package when the Windows Installer package is built.

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.

If this option is selected, an additional Windows Installer package will be created in the same directory as the .ism file and the other .msi file, with the naming convention of:

appname.isolated.msi

For more information on how Repackager isolates applications and the available isolation options, see Isolating Windows Installer Packages.

Note:This option is only enabled when the Create Microsoft Windows Installer Package option is selected and one of the following values is chosen:

• Single Compressed .MSI File
• .MSI File With External .CAB File
• Uncompressed .MSI File

Run Automated Tests on the Package

Select this option to automatically run best practice tests against the newly built Windows Installer package to determine if it is built according to Windows Installer standards, and if it is in compliance with the installation requirements of the Windows operating system.

Note:This option is only enabled when the Create Microsoft Windows Installer Package option is selected and any of the values except for Single Compressed Setup.exe File is chosen.

Create Microsoft App‑V Package

If this option is selected, after building a Windows Installer (.msi) file, a Microsoft App-V application will also be built.

Note:This option requires that you build a Windows Installer package.

Create VMware ThinApp Package

If this option is selected, after building a Windows Installer (.msi) file, a VMware ThinApp application will also be built.

Note:This option requires that you build a Windows Installer package.

Create Citrix XenApp Profile

If this option is selected, after building a Windows Installer (.msi) file, a Citrix profile compatible with Citrix XenApp will also be built.

Note:This option requires that you build a Windows Installer package.

Use the default Editor template

When building an InstallShield Editor project, select this option to use the default InstallShield Editor template.

A project template contains all of the default settings and design elements that you want to use as a starting point when you create an installation project.

Use a customized template

When building an InstallShield Editor project, select this option to specify a customized InstallShield Editor Project Template to use.

For example, if you wanted all of your InstallShield Editor projects to have a special custom dialog, a set of required redistributables, and a particular SQL script, you could create a project template that has all of those settings. Then, any time that you wanted to create a new project, you could base it off of your custom template. This enables you to avoid re-creating the custom dialog, re-adding the redistributables, and re-adding the SQL script every time that you create a new InstallShield Editor Project.

Build

Click to initiate the build process to build a Windows Installer package.

Repackaged Output Tasks

After an InstallShield Editor project and a Windows Installer package has been built, you can use these links to perform the following tasks:

• Modify the Editor project—Open this Repackager project’s associated InstallShield Editor project in InstallShield Editor.
• Modify the Windows Installer package—Open this Repackager project’s associated Windows Installer package in InstallShield Editor.

Once you have built the Windows Installer package and/or InstallShield Editor file, you can launch InstallShield Editor from the Repackaged Output area of the view.