Using Captured Applications with Other System Components
Captured applications can interact with other components installed on the desktop.
Performing Paste Operations
Review the following paste operations and limitations with ThinApp:
Pasting content from system installed applications to captured applications – This paste operation is unlimited. The virtual application can receive any standard clipboard formats, such as text, graphics, and HTML. The virtual application can receive Object Linking and Embedding (OLE) objects.
Pasting from captured applications to system applications – ThinApp converts OLE objects created in virtual applications to system native objects when you paste them into native applications.
Accessing Printers
A captured application has access to any printer installed on the computer that it is running on. Captured applications and applications installed on the physical system have the same printing ability.
You cannot use ThinApp to virtualize printer drivers. You must manually install printer drivers on a computer.
Accessing Drivers
A captured application has full access to any device driver installed on the computer that it is running on. Captured applications and applications installed on the physical system have the same relationship with device drivers. If an application requires a device driver, you must install the driver separately from the ThinApp package.
Sometimes, an application without an associated driver might function with some limitations. For example, Adobe Acrobat installs a printer driver that enables applications system wide to render PDF files using a print mechanism. When you use a captured version of Adobe Acrobat, you can use it to load, edit, and save PDF files without the printer driver installation. Other applications do not detect a new printer driver unless the driver is installed.
Accessing the Local Disk, the Removable Disk, and Network Shares
When you create a project structure, ThinApp configures isolation modes for directories and registry sub trees. The isolation modes control which directories the application can read and write to on the local computer.
Review the default configuration options described in Default Configuration Options.
An example of a hard disk is C:\. Isolation modes selected during the capture process affect access. Users can write to their Desktop and My Documents folders. Other modifications that the application makes go into the user sandbox. The default location of the sandbox is in the Application Data directory.
Accessing the System Registry
By default, captured applications can read the full system registry as permitted by access permissions. Specific parts of the registry are isolated from the system during the package creation process. This isolation reduces conflicts between different versions of virtual applications and system-installed applications. By default, ThinApp saves all registry modifications from captured applications in an isolated sandbox and the system remains unchanged.
Accessing Networking and Sockets
Captured applications have standard access to networking features. Captured applications can bind to local ports and make remote connections if the user has access permissions to perform these operations.
Using Shared Memory and Named Pipes
Captured applications can interact with other applications on the system by using shared memory, named pipes, mutex objects, and semaphores.
ThinApp can isolate shared memory objects and synchronization objects. This isolation makes them invisible to other applications, and other application objects are invisible to a captured application.
Using COM, DCOM, and Out-of-Process COM Components
Captured applications can create COM controls from the virtual environment and the system. If a COM control is installed as an out-of-process COM, the control runs as a virtual process when a captured application uses it. You can control modifications that the captured applications make.
Starting Services
Captured applications can start and run system-installed services and virtual services. System services run in the virtual environment that controls the modifications that the services can make.
Using File Type Associations
Captured applications can run system-installed applications by using file type associations. You can add file type associations to the local computer registry to point to captured executable files for individual users and machines.