Build Output for App-V Packages

InstallShield 2016 » Microsoft App-V Assistant

Edition • The Microsoft App-V Assistant is included in the Premier Edition of InstallShield.

Version • Some functionality is specific to particular versions of App-V packages. Version-specific differences are noted where appropriate.

Location of the Build Output

If you build an App-V 5.x package, InstallShield saves the App-V output in the following directory path:

App-VPackage\ProductName

If you build an App-V 4.x package, InstallShield saves the App-V output in the following directory path:

App-VPackage\ProductName_vN

The version number (N) of the App-V 4.x package is appended to the end of that folder path. Each time that you build an upgrade, InstallShield creates a new subfolder and increments the version number in the name of the subfolder.

The default location of the App-VPackage folder depends on whether you are building an App-V 5.x or 4.x package from within an MSI Database project or a Basic MSI project:

If you are building an App-V package from within an MSI Database project (.msi file), InstallShield creates the App-VPackage folder in the same folder as the .msi file.
If you are building an App-V package from an .ism file, InstallShield creates the App-VPackage folder in the following location:

InstallShield Project Folder\ProjectName\Product Configuration\Release Name\DiskImages\Disk1

Contents of the Build Output

If you are building an App-V package from within InstallShield, the output of the build consists of the following:

An App-V package—For information on the files that are included in an App-V package, see Components of an App-V Package.
A Windows Installer–based installation—Note that this is built only if you are building an App-V package from within a Basic MSI project. If you are building an App-V package from within an MSI Database project in InstallShield, InstallShield does not build this file.
A new Basic MSI project that assists in the distribution of the App-V package—This is built if you choose to generate an installation package as part of the build process.

InstallShield creates the new Basic MSI project in the release folder. Note the following details about this project:

The project contains dynamic file links to the App-V package files.
The properties and directories are updated in the project.
The Releases view contains four or more releases that enable you to build different combinations of releases (for example, compressed or uncompressed, with or without an InstallShield prerequisite for the App-V client).
A built release is also included with the new Basic MSI project. Any warnings or errors from this build are included as warning -9150 or error -9151 in the App-V project.
You can use this project if you want to add more functionality to your Windows Installer package. For example, you can create major upgrades, digitally sign the package, and more.
You can update the end-user license agreement (EULA) with your own custom EULA. The EULA that is included by default contains instructions that explain how to replace the default EULA text with your own EULA text.
This project is overwritten each time that you rebuild your App-V project.

Note • For troubleshooting information about resolving errors and warnings that you may encounter when you are building a virtual application, see Virtualization Conversion Errors and Warnings.