Specifying Package Feature Block Optimizations

InstallShield 2015 » Microsoft App-V Assistant

Edition: The Microsoft App-V Assistant is included in the Virtualization Pack.

You can use the package optimization to control the performance and network traffic that is associated with running an App-V package. The package optimization support you select determines how quickly the App-V package launches, and how often additional functionality needs to be streamed to the client while the App-V package is being used.

The files in an App-V package can be grouped into two feature blocks:

Feature block 1—Feature block 1 must contain the core functionality of the App-V package that is necessary to launch the application. At application launch, all of the files in feature block 1 are streamed to the client in one unit.
Feature block 2—Feature block 2 can contain additional functionality of the App-V package that is not necessary to launch the application. While the App-V package is being used, the files in feature block 2 can be streamed in small packets on an as-needed basis.

You can either choose to include all App-V package files in feature block 1 or, to improve launch speed, you can choose to group the files into two feature blocks: feature block 1 and feature block 2.

You indicate your package optimization preference on the Package Optimizations dialog box, which is opened by clicking the Package Optimizations link in the More Options area on the Build Options page.

The Package Optimizations dialog box includes the following options:

Package Optimizations Options

Option

Description

Optimize for Streaming

If you choose this option, the Microsoft App-V Assistant will perform a static analysis of the shortcuts in the application and decide which files should be in feature block 1 and which should be in feature block 2.

This option provides a relatively quick launch time while limiting network traffic during application use.

Note: When application files are streamed to a client either at launch or during application use, they are saved in the App-V cache and do not need to be streamed again during subsequent use of the application.

Optimize for Offline Use

If you choose this option, all files in the App-V package will be included in feature block 1 and will be streamed to the client at startup in one file before the application launches. After that, no more streaming is done. All files are stored in the App-V cache, which means that the application is available for use even when the machine is not connected to the App-V server.

Select this option if you want to enable end users to use the App-V package when not connected to the App-V server and if you want to eliminate network traffic when the App-V package is being used.

Note: When application files are streamed to a client either at launch or during application use, they are saved in the App-V cache and do not need to be streamed again during subsequent application use.