4.7.3

Configuring Objects and DLL Files 9
You can modify ThinApp parameters to specify COM object access and DLL loading requirements.
This chapter includes the following topics:
n
“ExternalCOMObjects Parameter,” on page 33
n
“ExternalDLLs Parameter,” on page 34
n
“ForcedVirtualLoadPaths Parameter,” on page 34
n
“IsolatedMemoryObjects Parameter,” on page 35
n
“IsolatedSynchronizationObjects Parameter,” on page 35
n
“NotificationDLLs Parameter,” on page 36
n
“NotificationDLLSignature Parameter,” on page 36
n
“ObjectTypes Parameter,” on page 37
n
“SandboxCOMObjects Parameter,” on page 37
n
“VirtualizeExternalOutOfProcessCOM Parameter,” on page 37
ExternalCOMObjects Parameter
The ExternalCOMObjects parameter determines whether Windows creates and runs COM objects in the
physical environment, rather than the virtual environment, to facilitate application compatibility with
ThinApp.
COM objects that are external to the virtual environment always run in the physical environment.
ThinApp sets an initial value for the ExternalCOMObjects parameter that creates and runs the COM objects in
the virtual environment.
COM supports out-of-process executable servers and service-based COM objects. If an application can create
COM objects that generate modifications on the host computer, the integrity of the host computer is at risk. If
ThinApp runs out-of-process and service-based COM objects in the virtual environment, all changes that the
COM objects make are stored by ThinApp in the sandbox.
The capture process does not generate this parameter. You can add this parameter to the Package.ini file under
the [BuildOptions] section.
Example: Running COM Objects Outside the Virtual Environment
When you troubleshoot a problem with VMware support and determine that an application implements COM
objects that are incompatible with ThinApp, you can modify the ExternalCOMObjects parameter to run the
COM objects outside the virtual environment.
VMware, Inc.
33