Upgradepath; Virtualdrives - VMware THINAPP 4.6 Manual

Examples
You can modify the CachePath parameter to use an absolute path.
CachePath=C:\VirtCache
You can set a relative path that ThinApp detects as the path relative to the directory where the application
executable file resides. If the package resides in C:\VirtApps and the CachePath parameter has a value of
Cache, the cache directory is C:\VirtApps\Cache.
CachePath=Cache
When you use a USB device and move the sandbox on to the USB device, you might move the cache to the USB
device to avoid interfering with the local machine. In this example, the cache and sandbox exist in the same
directory level.
CachePath=<sandbox_path>

UpgradePath

The UpgradePath parameter specifies the location of information and files for Application Sync and integer
updates.
ThinApp sets an initial value that causes the Application Sync utility to place log and cache files in the same
location as the application executable file on the local machine. Integer updates operate in the same way with
files.
When the Application Sync utility downloads an update from a server, it stores the update with a temporary
name in the UpgradePath location. The next time the application starts, ThinApp renames the temporary file
with a .1 extension or a .2 extension depending on whether .1 already exists. ThinApp attempts to change the
name with the .1 extension to the original name of the file that might reside in another directory. If ThinApp
cannot make this change, the file keeps the .1 extension in the UpgradePath location. Running the original
application accesses that file.
For information about the Application Sync utility, see "Application Sync Updates" on page 53.
Examples
When the default location has limited space, such as a USB device, or you want to isolate upgrades from the
application executable file, you can modify the UpgradePath parameter to specify another location to detect
update files. The parameter can include environment variables in the path but cannot support folder macros.
[BuildOptions]
UpgradePath=C:\Program Files\<my_app_upgrades>

VirtualDrives

The VirtualDrives parameter specifies additional drive letters that are available to the application at
runtime.
ThinApp makes the virtual environment resemble the physical capture environment and mimics the physical
drives that are available on the capture system. ThinApp represents virtual drives through the
VirtualDrives parameter and a project folder, such as %drive_<drive_letter>%, that contains the virtual
files on the drive. This project folder can reside in the read‐only file system of the package and in the sandbox
when write operations cannot occur on the physical drive.
The VirtualDrives parameter presents the drives to the application at runtime. The VirtualDrives
parameter displays metadata about the drive, such as a the serial number and type of drive. For example,
ThinApp detects the physical C: drive on the capture system and enters it into the parameter as a FIXED type
of drive with the serial number.
VMware, Inc.
Chapter 5 Configuring Package Parameters
79