VMware THINAPP 4.6 - MIGRATING APPLICATIONS TECHNICAL NOTE, Руководство пользователя

Страница: 77 / 146

VMware, Inc. 77
Chapter 5 Configuring Package Parameters
NotificationDLLs
The NotificationDLLs parameter makes calls to third ‐ party DLL files to provide notification of events, such
as application startup or shutdown. The DLLs can reside on the physical file system or the virtual package.
If ThinApp cannot load a DLL file, the package generates errors.
This parameter does not appear in the Package.ini file. ThinApp SDK users can add this parameter to the file.
Examples
You can modify the NotificationDLLs parameter to make calls to the First.dll and Second.dll files.
[BuildOptions]
NotificationDLLs=First.dll;Second.dll
NotificationDLLSignature
The NotificationDLLSignature parameter works with the NotificationDLLs parameter and verifies that
a specified DLL file has a signature. If the DLL does not have a signature, ThinApp does not load the file.
Example
You can modify the NotificationDLLSignature parameter with an asterisk (*) to ensure that the DLL file is
authenticode ‐ signed.
[BuildOptions]
NotificationDLLSignature=*
You can set an entity to ensure that the DLL is signed by that entity.
[BuildOptions]
NotificationDLLSignature=VMware, Inc.
ObjectTypes
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 generated by the capture process.
Examples
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
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.