4.7.3
Table Of Contents
- ThinApp Package.ini Parameters Reference Guide
- Contents
- About This Guide
- Configuring Package Parameters
- Package.ini File Structure
- Package.ini or ##Attributes.ini Files That Override Package.ini Settings
- Configuring the ThinApp Runtime
- Configuring Isolation
- Configuring File and Protocol Associations
- Configuring Build Output
- Configuring Permissions
- Configuring Objects and DLL Files
- ExternalCOMObjects Parameter
- ExternalDLLs Parameter
- ForcedVirtualLoadPaths Parameter
- IsolatedMemoryObjects Parameter
- IsolatedSynchronizationObjects Parameter
- NotificationDLLs Parameter
- NotificationDLLSignature Parameter
- ObjectTypes Parameter
- SandboxCOMObjects Parameter
- VirtualizeExternalOutOfProcessCOM Parameter
- Configuring File Storage
- Configuring Processes and Services
- Configuring Sizes
- Configuring Logging
- Configuring Versions
- Configuring Locales
- Configuring Individual Applications
- Configuring Dependent Applications Using the Application Utility
- Configuring Application Updates with the Application Sync Utility
- Configuring MSI Files
- Configuring Sandbox Storage and Inventory Names
- Other Configuration Parameters
- Locating the ThinApp Sandbox
- Controlling the Sandbox Location
- Sandbox Structure
- Creating ThinApp Snapshots and Projects from the Command Line
- Index
Sandbox Structure 24
ThinApp stores the sandbox using a file structure almost identical to the build project structure. ThinApp uses
macro names for shell folder locations, such as %AppData%, instead of hard coded paths.
This structure enables the sandbox to migrate to different computers dynamically when the application runs
from new locations.
The sandbox contains the following registry files:
Registry.rw.tvr
Contains all registry modifications that the application makes.
Registry.rw.lck
Prevents other computers from simultaneously using a registry located on a
network share.
Registry.tvr.backup
Contains a backup of the .tvr file that ThinApp uses when the original .tvr file
is corrupted.
In addition to these registry files, the sandbox contains directories that include %AppData%, %ProgramFilesDir
%, and %SystemRoot%. Each of these folders contains modifications to respective folders in the captured
application.
You can make changes to files in the sandbox under specific conditions, as described in these topics.
n
Making Changes to the Sandbox on page 85
VMware does not support modifying or adding files directly to the sandbox. If you copy files to the
sandbox directory, the files are not visible to the application.
n
Listing Virtual Registry Contents with vregtool on page 86
Because the sandbox contains the modifications to the registry, you might need the vregtool utility to
view modified virtual registry changes.
Making Changes to the Sandbox
VMware does not support modifying or adding files directly to the sandbox. If you copy files to the sandbox
directory, the files are not visible to the application.
ThinApp stores file system information in the virtual registry. The virtual registry enables ThinApp to optimize
file system access in the virtual environment. For example, when an application tries to open a file, ThinApp
does not have to consult the real file system for the real system location and again for the sandbox location.
Instead, ThinApp can check for the existence of the file by consulting only the virtual registry. This ability
increases the ThinApp runtime performance.
If a file already exists in the sandbox, you can overwrite and update the file. VMware recommends that you
perform all modifications from the application itself.
VMware, Inc.
85