5.1
Table Of Contents
- ThinApp Package.ini Parameters Reference Guide
- Contents
- About This Guide
- Configuring Package Parameters
- Package.ini File Structure
- Package.ini or ##Attributes.ini Files That Override Package.ini Settings
- Configuring the ThinApp Runtime
- Configuring Isolation
- Configuring File and Protocol Associations
- Configuring Build Output
- Configuring Permissions
- Configuring Objects and DLL Files
- ExternalCOMObjects Parameter
- ExternalDLLs Parameter
- ForcedVirtualLoadPaths Parameter
- IsolatedMemoryObjects Parameter
- IsolatedSynchronizationObjects Parameter
- NotificationDLLs Parameter
- NotificationDLLSignature Parameter
- ObjectTypes Parameter
- SandboxCOMObjects Parameter
- VirtualizeExternalOutOfProcessCOM Parameter
- Configuring File Storage
- Configuring Processes and Services
- Configuring Sizes
- Configuring Logging
- Configuring Versions
- Configuring Locales
- Configuring Individual Applications
- Configuring Dependent Applications Using the Application Utility
- Configuring Application Updates with the Application Sync Utility
- Configuring MSI Files
- Configuring Sandbox Storage and Inventory Names
- Other Configuration Parameters
- DisableCutPaste Parameter
- LoadDotNetFromSystem Parameter
- PermittedComputers Parameter
- Services Parameter
- StatusbarDisplayName Parameter
- DisableTransactionRegistry Parameter
- PreventDLLInjection
- ProcessExternalNameBehavior Parameter
- PreventDllInjectionExceptions Parameter
- LargeAddressAware Parameter
- PermittedComputers Parameter
- PermittedComputersAccessDeniedMsg Parameter
- PermittedComputersOfflineAccess Parameter
- IgnoreDDEMessages Parameter
- Locating the ThinApp Sandbox
- Controlling the Sandbox Location
- Sandbox Structure
- Creating ThinApp Snapshots and Projects from the Command Line
- Index
You can import a single package located in the same directory as the base executable file.
RequiredAppLinks=Plugin.exe
You can import a single package located in a subdirectory of the base executable file.
RequiredAppLinks=plugins\Plugin.exe
You can import all executable files located in the directory for plug-in files. If ThinApp cannot import any
executable file because the file is not a valid Thinapp package or because a security problem exists, the base
executable file fails to load.
RequiredAppLinks=plugins\*.exe
You can import all executable files located at the n:\plugins absolute path.
RequiredAppLinks=n:\plugins\*.exe
You can expand the PLUGINS environment variable and import all executable files at this location.
RequiredAppLinks=%PLUGINS%\*.exe
You can load two specified plug-in files and a list of executable files located under the plug-in location.
RequiredAppLinks=plugin1.exe;plugin2.exe;plugins\*.exe
OptionalAppLinks Parameter
The OptionalAppLinksparameter is similar to the RequireAppLinks parameter but ignores errors and starts
the main application even when an import operation fails.
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. You can specify absolute paths, such as C:\abs\path\dotnet.exe, relative paths, such as
relpath\dotnet.exe, and UNC paths, such as \\server\share\dotnet.exe.
RequireAppLinks and OptionalAppLinksparameters use the same syntax. For information about the
RequireAppLinksparameter and examples, see “RequiredAppLinks Parameter,” on page 62.
When using the Application Link utility via the OptionalAppLinks parameter, the base package and linked
dependencies must be built with the same version of ThinApp. To upgrade older packages to include the
latest version of the ThinApp runtime, use the relink.exe command-line utility included with ThinApp.
Chapter 18 Configuring Dependent Applications Using the Application Utility
VMware, Inc. 63