5.1

n
Path names can include spaces.
n
Path names can specify multiple links or dependencies with a semicolon that separates individual
filenames. An example is RequiredAppLinks=Dependency1.exe; Dependency2.exe;.
n
Path names can contain asterisk and query wildcard characters (* and ?) in filenames and directory
paths. For example, RequiredAppLinks=WildPath*\WildFilename*.dat.
If a path containing a wildcard character matches more than one directory in the file system, each
matching directory name will be returned, to enable additional path or filename matching.
Wildcards that are used in combination with environment variables can provide powerful customized
recursive searching for dependent applications. For example, OptionalAppLinks=%HOMEPATH
%\OfficePlugins\*\*.
RequiredAppLinks Parameter
The RequiredAppLinksparameter specifies a list of required packages to import to the base package at
runtime. You can configure this parameter in the Package.ini file of the base package.
If the import operation for any dependent package fails, an error message appears and the base executable
file exits. You can use the OptionalAppLinks parameter instead to continue even when load errors occur. If
you use a wildcard pattern to specify a package and files do not match the wildcard pattern, ThinApp does
not generate an error message.
Importing packages involves the following operations:
n
Running VBScripts from imported packages
n
Starting autostart services from imported packages
n
Registering fonts from imported packages
n
Relocating SxS DLL files from Windows XP to Windows Vista
You must create a link to the primary data container of a package. You cannot link to other shortcut
packages.
Path names are on the deployment machine because the linking takes effect at runtime on the client
machine. Use semicolons to separate the linked packages. For information about pathname formats, see
“Application Link Pathname Formats,” on page 61.
Example: Link the Application to .NET
If you package the .NET framework in the dotnet.exe package and you have a .NET application, you can
specify that the application needs to link to the dotnet.exe file before it can start.
RequiredAppLinks=C:\abs\path\dotnet.exe
You can specify a relative path.
RequiredAppLinks=<relative_path>\dotnet.exe
You can specify a UNC path.
RequiredAppLinks=\\server\share\dotnet.exe
You can use ThinApp folder macros in the path value.
RequiredAppLinks=%SystemSystem%\Package.dat
You can use environment variables in the path value. The risk of using environment variables is that a user
might change the values before starting the application and create an Application Link dependency other
than the one that the administrator set up.
RequiredAppLinks=%MyEnvironmentVariable%\Package.dat
ThinApp Package.ini Parameters Reference Guide
62 VMware, Inc.