The IsolatedSynchronizationObjects parameter lists the synchronization objects to isolate from other applications.
Synchronization objects coordinate actions between applications. The following Windows synchronization objects might appear in logs for application errors:
OpenMutexCreateMutexOpenSemaphoreCreateSemaphoreOpenEventCreateEvent
If these objects appear in log files, you might isolate the objects in the virtual environment to avoid a collision with synchronization objects that native applications create.
You can isolate synchronization objects from applications that do not run in the same virtual namespace. If two applications share the same sandbox path, the applications have the same namespace for isolated synchronization objects. If two applications have the same sandbox name, but different sandbox paths, the applications have separate namespaces.
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 (;).
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
Was this page helpful?