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
Configuring Individual Applications 17
You can modify ThinApp parameters to configure specific applications.
Parameters specific to entry points are specified under the [<application>.exe]sections of the Package.ini
file. For example, the entries under Adobe Reader 8.exe for an Adobe Reader application might affect
command-line arguments and application shortcuts.
This chapter includes the following topics:
n
“CommandLine Parameter,” on page 57
n
“Disabled Parameter,” on page 58
n
“ReadOnlyData Parameter,” on page 58
n
“Shortcut Parameter,” on page 58
n
“Shortcuts Parameter,” on page 59
n
“Source Parameter,” on page 59
n
“WorkingDirectory Parameter,” on page 60
CommandLine Parameter
The CommandLine parameter specifies the command-line arguments that start a shortcut executable file.
While the Source parameter specifies the path to the shortcut executable file, the CommandLine parameter
specifies the file with the required options or parameters to start it.
If the Start menu shortcut for the application has command-line options, the capture process sets the initial
value of the CommandLine parameter based on those options. In rare troubleshooting cases with technical
support, you might alter this parameter. The options and parameters follow the base application name.
Depending on the application, use / or - before the option or parameter. Use folder macros for the pathname
conventions.
Example: Modifying a CommandLine Parameter
You can modify the AnsiCodePage parameter with an entry based on the C:\Program Files\Mozilla
Firefox\firefox.exe -safe-mode Start menu shortcut.
CommandLine="C:\Program Files\Mozilla Firefox\firefox.exe" -safe-mode Command-line arguments can
use the /<option> <parameter>format.
[<app>.exe]
Source=%ProgramFilesDir%\<base_app>\<app>.exe
Shortcut=<primary_data_container>.exe
CommandLine="%ProgramFilesDir%\<base_app>\<app>.exe" /<option> <parameter>
VMware, Inc.
57