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
Example: Supporting Write Operations From Virtual Processes to Native
Processes
You can add the AllowExternalProcessModifications parameter to the Package.ini file to support write
operations from virtual processes to native processes. For example, a speech recognition application must
inject itself into native applications to voice the text.
[BuildOptions]
AllowExternalProcessModifications=1
AutoShutdownServices Parameter
The AutoShutdownServices parameter controls whether to shut down virtual services when the last non-
service process exits.
ThinApp sets an initial value to stop virtual services when the last non-service process exits. The parameter
does not affect services outside the virtual context.
Example: Keeping a Virtual Service Running After the Application Exits
You can modify the AutoShutdownServices parameter when you run Apache Web Server and want to keep
the virtual service running after the application that starts the service exits.
[BuildOptions]
AutoShutdownServices=0
AutoStartServices Parameter
The AutoStartServices parameter controls whether to start the virtual services when the first virtual
application starts.
ThinApp sets an initial value that starts the virtual services that are installed with the automatic startup type
option. The virtual services start when the user runs the first parent process.
Example: Preventing a Virtual Service From Starting
When applications install a service, but do not use it, you can modify the AutoStartServices parameter to
prevent the start of the virtual service and save time.
[BuildOptions]
AutoStartServices=0
ChildProcessEnvironmentDefault Parameter
The ChildProcessEnvironmentDefault parameter determines whether ThinApp runs all child processes in
the virtual environment.
ThinApp creates all child processes in the virtual environment. If the processes are slow, you might want to
move child processes to the physical environment. As a child process, Microsoft Outlook might affect
performance when it copies the whole mailbox to the virtual environment.
You can create specific exceptions with the ChildProcessEnvironmentExceptions parameter.
See “ChildProcessEnvironmentExceptions Parameter,” on page 45.
ThinApp Package.ini Parameters Reference Guide
44 VMware, Inc.










