VMware THINAPP 4.6 - MIGRATING APPLICATIONS TECHNICAL NOTE, Manual

Page: 111 / 146

VMware, Inc. 111
8
ThinApp stores the differences between snapshots during the setup capture process in a virtual file system and
virtual registry. The virtual file system uses folder macros to represent Windows shell folder locations.
This information about the virtual file system includes the following topics:

“Virtual File System Formats” on page 111

“ThinApp Folder Macros” on page 111
Virtual File System Formats
ThinApp generates the following virtual file system formats:

Build
The setup capture process generates this format from files found directly on the physical file system.
ThinApp uses folder macros to represent Windows shell folder locations.

Embedded
The build.bat file triggers a build process that embeds a read ‐ only file system in executable files.
The executable files provide block ‐ based streaming to client computers. ThinApp compresses the file
system.

Sandbox
Running the captured application generates the read ‐ write directory structure that holds file data that the
application modifies. File modifications that prompt ThinApp to extract embedded virtual files to the
sandbox include the following operations:

Changing the time stamp or attributes of a file

Opening a file with write access

Truncating a file

Renaming or moving a file
The embedded and sandbox file systems use folder macros to enable file paths to dynamically expand at
runtime.
ThinApp Folder Macros
ThinApp uses macros to represent file system path locations that might change when virtualized applications
run on different Windows operating systems or computers. The use of macros enables shared application
profile information to instantly migrate to different operating systems.
ThinApp File System Formats and
Macros
8