Enabling Thinapp Application Building When In Direct Edit Mode; Including Additional Windows Installer Packages In A Thinapp Application - Novell ADMINSTUDIO 9.5 User Manual

Hide thumbs Also See for ADMINSTUDIO 9.5:

Table of Contents

Chapter 10: Creating Customized Virtual Applications

Creating ThinApp Applications

build that particular release, you want to also build a ThinApp application for that release. However, the releases

that are selected on the Build Options page have no bearing upon which release is built when you click the

Build button on the toolbar. When you initiate a build by clicking the Build button, a build is initiated for the

active release—the release that was most recently selected on the Installation Designer Releases view. The

output of that build would depend upon what releases were selected on the Build Options page:

Active release selected—A Windows Installer package and a ThinApp application would be built.

Active release not selected—Only a Windows Installer package would be built.

Enabling ThinApp Application Building When in Direct Edit Mode

When you are editing a Windows Installer (

are in Direct Edit Mode or Direct MST Mode. Because you are directly editing a Windows Installer package, you

save your changes by selecting Save on the File menu. It not necessary to build the package, because it is

already built. Therefore, InstallShield's Build function is disabled.

However, you do need to run the build process to build a ThinApp application for this Windows Installer package.

To do this, perform the following steps:

To enable ThinApp application building when in Direct Edit Mode:

Open a Windows Installer package or a transform file in InstallShield. It will be opened in Direct Edit Mode or

Direct MST Mode, and the Build function (Build on the Build menu and the Build toolbar button) will be

Open the Build Options page of the ThinApp Assistant.

Select the Build ThinApp application option. After you select this option, the Build ThinApp application

selection on the Build menu becomes enabled, as does the Build toolbar button.

Sometimes a primary Windows Installer package uses other Windows Installer packages indirectly, such as driver

files, client components, etc. In addition to being able to convert a single Windows Installer package to a virtual

package, you can also use the ThinApp Assistant to convert an application suite of multiple Windows Installer

packages into one virtual package.

To include additional Windows Installer packages in a ThinApp application, set the Would you like to include

additional MSI files in the virtual package? option on the Build Options page to Yes, and then select the

packages that you want to add.

When you select a release on the Build Options page, you are specifying that whenever you

To build more than one release at a time, perform a batch build. See Performing Batch Builds.

) package or a transform (

) file in the ThinApp Assistant, you

ADS-0950-UG00

AdminStudio 9.5 User Guide