5.1

The IsolatedSynchronizationObjects parameter does not appear in the Package.ini file, but you can add the
parameter. ThinApp sets an initial value that makes synchronization objects accessible to other applications.
Virtual applications with different sandboxes can detect the synchronization objects.
The IsolatedSynchronizationObjects parameter accepts a list of entries that are separated by a semicolon
(;).
Example: Isolating a Synchronization Object
You can modify the IsolatedSynchronizationObjects parameter to isolate the synchronization object with
the My Shared Object name and the synchronization object with outlook in the name.
[BuildOptions]
IsolatedSynchronizationObjects=*outlook*;My Shared Object
NotificationDLLs Parameter
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. However, ThinApp
SDK users can add this parameter to the file.
Example: Making Calls to DLL Files
You can modify the NotificationDLLs parameter to make calls to the First.dll and Second.dll files.
[BuildOptions]
NotificationDLLs=First.dll;Second.dll
NotificationDLLSignature Parameter
The NotificationDLLSignature parameter works with the NotificationDLLs parameter and verifies that a
specified DLL file has a signature.
If the DLL lacks a signature, ThinApp does not load the file.
Example: Ensuring That a DLL File is Authenticode-signed
You can modify the NotificationDLLSignature parameter with an asterisk (*) to ensure that the DLL file is
authenticode-signed.
[BuildOptions]
NotificationDLLSignature=*
Example: Ensuring That a DLL File is Entity-signed
You can set an entity to ensure that the DLL is signed by that entity.
[BuildOptions]
NotificationDLLSignature=VMware, Inc.
ThinApp Package.ini Parameters Reference Guide
36 VMware, Inc.