User`s guide

You can list the CLSID keys.
[BuildOptions]
ExternalCOMObjects={8BC3F05E-D86B-11D0-A075-00C04FB68820};{7D096C5F-AC08-4F1F-BEB7-5C22C517CE39}
ExternalDLLs Parameter
The ExternalDLLs parameter can force Windows to load specific DLL files from the virtual file system.
ThinApp sets an initial value that loads DLL files from the virtual file system and passes the loading process
to Windows for DLL files on the physical file system. In some circumstances, Windows must load a DLL file
in the virtual file system. You might have a DLL file that inserts itself into other processes using Windows
hooks. The DLL file that implements the hook must be available on the host file system and Windows must
load that file. When you specify a DLL file in the ExternalDLLs parameter, ThinApp extracts the file from the
virtual file system to the sandbox and instructs Windows to load it.
Virtual dictation software is a type of software that might interface with native applications that pass
information between DLLs. ThinApp can pass the loading of DLLs in the virtual environment to Windows to
ensure that local applications can interface with the DLLs.
The ExternalDLLs parameter does not support a DLL file that depends on other DLL files in the virtual file
system. In this case, Windows cannot load the DLL file.
Example: Forcing Windows to Load DLL Files From the Virtual File System
You can modify the ExternalDLLs parameter to force Windows to load the inject.dll and injectme2.dll files
from the virtual file system.
[BuildOptions]
ExternalDLLs=inject.dll;injectme2.dll
ForcedVirtualLoadPaths Parameter
The ForcedVirtualLoadPaths parameter instructs ThinApp to load DLL files as virtual DLL files even if the
files reside outside the package. This parameter is useful when an application must load external system DLL
files that depend on DLL files located in the package.
The DLL paths can contain macros. Use semicolons to separate multiple paths.
This parameter achieves the same result as the AddForcedVirtualLoadPath API function. See
Example: Forcing ThinApp to Load DLLs in the Virtual Environment
You can modify the ForcedVirtualLoadPaths parameter when you have an application that depends on
external DLL files.
When you capture Microsoft Office without Microsoft Outlook and a native version of Microsoft Outlook exists
on the local system, you cannot send email from the virtual version of Microsoft Excel because the native
envelope.dll file that is installed with Microsoft Outlook depends on the mso.dll file that ThinApp loads in
the virtual environment. You can force ThinApp to load the envelope.dll file in the virtual environment instead
of in the native environment.
[BuildOptions]
ForcedVirtualLoadPaths=%ProgramFilesDir%\Microsoft Office\Office10\envelope.dll
ThinApp Package.ini Parameters Reference Guide
34 VMware, Inc.