5.1

ObjectTypes Parameter
The ObjectTypes parameter specifies a list of virtual COM object types that are visible to other applications
in the physical environment. You can use scripts, such as VBScripts, to call objects that start captured
applications.
An object type is registered to only one native or virtual application at a time. If you install Office 2003 on
the native machine and want to use a virtual Office 2007 package, you must determine whether to have the
virtual or native application handle the object types.
If you want the virtual Office 2007 to handle the object types, you can leave the ObjectTypes setting in the
Package.ini file, build the package, and register it using the thinreg.exe utility. If you want the native
Office 2003 to handle the object types, you must remove the ObjectTypes setting from the Package.ini file
before building and registering the package.
You cannot add random entries to the ObjectTypes parameter.
You can only remove entries that were generated by the capture process.
Example: Starting a Virtual Application When a COM Object is Created
If a script or a native application creates an Excel.Application COM object or other COM objects listed in
the ObjectTypes parameter, ThinApp starts the virtual package.
[Microsoft Office Excel 2007.exe]
ObjectTypes=Excel.Application;Excel.Application.12;Excel.Chart;
Excel.Macrosheet;Excel.Sheet; Excel.Workspace
SandboxCOMObjects Parameter
The SandboxCOMObjects parameter indicates whether applications in the physical environment can access
COM objects that the virtual application registers at runtime.
ThinApp sets an initial value that prevents native applications in the physical environment from accessing
COM objects that the virtual application registers. ThinApp places COM objects that the virtual application
registers in the sandbox.
Example: Making COM Objects Registered Outside the Sandbox Visible
You can modify the SandboxCOMObjects parameter to make visible the COM objects that the virtual
application registers outside the sandbox.
For example, if you install native Microsoft Office 2003 and virtual Microsoft Office 2007, and you run a
custom mail merge program in the native environment that starts Microsoft Word and instructs it to open,
change, and save a document, you can generate Microsoft Word 2007 documents when virtual Microsoft
Word is running. The native application can access COM objects from the virtual application.
SandboxCOMObjects=0
VirtualizeExternalOutOfProcessCOM Parameter
The VirtualizeExternalOutOfProcessCOM parameter controls whether out-of-process COM objects can run
in the virtual environment.
COM objects that are external to the virtual environment always run in the physical environment.
This parameter addresses out-of-process COM objects that are not part of a ThinApp package and are not
registered in the virtual registry.
Chapter 10 Configuring Objects and DLL Files
VMware, Inc. 37