3
Capture Application B.
4
In the Package.ini file for Application B, specify Application C as a required or optional application link.
For example, add RequiredLinks=\AppFolder\AppC\AppC.exe to the file.
5
Capture Application C.
If you start Application A, it can access the files and registry keys of Application B and Application B can
access the files and registry keys of Application C.
Affecting Isolation Modes with Application Link
ThinApp loads an Application Link layer during application startup and merges registry entries and file
system directories. If ThinApp finds a registry subkey or file system directory that did not previously exist in
the main package or layer that is already merged, ThinApp uses the isolation mode specified in the layer being
loaded. If the registry subkey or file system directory exists in the main package and a layer that is already
merged, ThinApp uses the most restrictive isolation mode specified in any of the layers or main package.
The order of most restrictive to least restrictive isolation modes is Full, WriteCopy, and Merged.
PermittedGroups Effect on Linked Packages
If you link two applications and you specify a value for the PermittedGroups parameter, the user account
used for starting the application must be a member of at least one of the Active Directory groups for this
parameter in the Package.ini files of both applications. For information about the PermittedGroups
parameter, see "Configuring Permissions" on page 72.
Sandbox Changes for Standalone and Linked Packages
Sandbox changes from linked packages are not visible to the base executable file. For example, you can install
Acrobat Reader as a standalone virtual package and as a linked package to the base Firefox application. When
you start Acrobat Reader as a standalone application by running the virtual package and you change the
preferences, ThinApp stores the changes in the sandbox for Acrobat Reader. When you start Firefox, Firefox
cannot detect those changes because Firefox has its own sandbox. Opening a .pdf file with Firefox does not
reflect the preference changes that exist in the standalone Acrobat Reader application.
Import Order for Linked Packages
ThinApp imports linked applications according to the order of applications in the RequiredAppLinks or
OptionalAppLinks parameter. If either parameter specifies a wildcard character that triggers the import of
more than one file, alphabetical order determines which package is imported first.
The OptionalAppLinks parameter might appear as OptionalAppLinks=a.exe;b.exe;plugins\*.exe.
Using a.exe and b.exe as sample executable files, ThinApp imports linked packages in the order described
in Table
4‐1.
Table 4-1. Imported Linked Packages
Import
Order
Linked Package
1
Base application
2
a.exe
3
b.exe
4
Plug‐ins loaded in alphabetical order
5
Nested plug‐ins for a.exe
6
Nested plug‐ins for b.exe
7
Nested plug‐ins for the first set of plug‐ins in this list
For information about nested links, see "Set Up Nested Links with Application Link" on page 58.
VMware, Inc.
Chapter 4 Updating and Linking Applications
59