A
Application Link
A utility that links dependent applications to a base application at runtime and starts all the applications together when you start the base application. You can use the utility to deploy and update component packages separately rather than capture all components in the same package.
Application Sync
A utility that updates an application by detecting a new packaged version on a server or network share. You can configure update settings, such as the checking of an update server at certain intervals. ThinApp detects the most recent application executable file and downloads the differences.
attributes.ini
The file that applies configuration settings at the directory level of the package rather than the entire package. The ##Attributes.ini settings override the overall Package.ini settings.
B
build
To convert a ThinApp project into a package. You can build a package with the Setup Capture wizard or with the build.bat utility.
C
capture
To package an application into a virtual environment and set initial application parameters. ThinApp provides the Setup Capture wizard or the snapshot.exe utility to create a portable application package that is independent of the operating system it runs on.
clean machine
The computer or virtual machine, installed with only the basic Windows operating system, on which you capture the application. The Windows operating system version must be the earliest version of Windows that you expect the application to run on.
E
entry point
An executable file that starts the captured application. An application might have multiple entry points. For example, the Firefox.exe file might serve as an entry point for a Mozilla Firefox application. The primary data container file can exist within an entry point or as a .dat file.
I
inventory name
A name that ThinApp uses for internal tracking of the application. The inventory name sets the default project directory name and appears in the Add or Remove Programs dialog box for Windows.
isolation mode
A package setting that determines the read and write access to the physical environment. ThinApp has WriteCopy, Merged, and Full isolation modes.
L
logging.dll
A utility that generates .trace files.
Log Monitor
A utility that captures chronological activity for executable files that the captured application starts.The log_monitor.exe file is compatible only with applications captured using the same version of ThinApp.
M
MSI
A Windows Installer container that is useful for application deployment tools. You can deliver the captured application as an MSI file instead of an executable file.
N
native
Refers to the physical environment rather than the virtual environment. See also physical.
network streaming
The process of running a package from a central server. ThinApp downloads blocks of the application as needed to ensure quick processing and display.
P
package
The virtual application files that the ThinApp build process generates. The package includes the primary data container file and entry point files to access the application.
package.ini
The file that applies configuration settings to the package and that resides in the captured application folder. The Setup Capture wizard sets the initial values of the configuration settings.
physical
Refers to the computer memory and file system in which all standard Windows processes run. Depending on ThinApp isolation mode settings, processes in the virtual environment can access the physical environment. See also native, virtual.
postscan
To establish an image or snapshot of a machine after you install the application you want to capture. The capture process stores in a virtual file system and virtual registry the differences between the prescan and postscan images. See also prescan, snapshot.
prescan
To establish a baseline image or snapshot of a machine before you install the application you want to capture. The capture process stores in a virtual file system and virtual registry the differences between the prescan and postscan images. See also postscan, snapshot.
primary data container
The main virtual application file. The file is a .exe file or a .dat file that includes the ThinApp runtime and the read-only virtual file system and virtual registry. The primary data container must reside in the same /bin directory with any subordinate application executable files because entry points use the information in the primary data container.
project
The data that the capture process creates before you build a package. The capture process uses the inventory name as the default project directory name. You can customize parameters in the project files before you build an application package. You cannot deploy a captured application until you build a package from the project.
S
sandbox
The physical system folder that stores runtime user changes to the virtual application. When you start the application, ThinApp incorporates changes from the sandbox. When you delete the sandbox, ThinApp reverts the application to its captured state. The default location of the sandbox is %APPDATA%\Thinstall\<application_name>.
sbmerge.exe
A utility that makes incremental updates to applications, such as the incorporation of a plug-in or a change in a browser home page. The sbmerge.exe utility merges runtime changes recorded in the sandbox back into a ThinApp project.
snapshot
A recording of the state of the Windows file system and registry during the application capture process. The Setup Capture process uses the snapshot.exe utility to take a snapshot before and after the application is installed and stores the differences in a virtual file system and virtual registry. See also postscan, prescan.
snapshot.exe
A utility that creates the snapshots of a computer file system and registry and facilitates the prescan and postscan operations during the capture process. Only advanced users who build ThinApp functionality into other platforms might make direct use of this utility. See also postscan, prescan, snapshot.
snapshot.ini
A configuration file that specifies the directories and subkeys to exclude from a ThinApp project when you capture an application. You can customize this file for applications.
T
template.msi
A template for MSI files that you can customize to adhere to company deployment procedures and standards. For example, you can add registry settings for ThinApp to add to client computers as part of the installation.
thinreg.exe
A utility that establishes file type associations, sets up Start menu and desktop shortcuts, and facilitates the opening of files. You must run the thinreg.exe utility to register executable files. MSI files automate the thinreg.exe registration process.
tlink.exe
A utility that links key modules during the build process.
V
vftool.exe
A utility that compiles the virtual file system during the build process.
virtual
Refers to the logical file and memory within which a captured application runs. Processes in a physical environment cannot access the virtual environment. See also physical.
virtual application
An application that you capture to make it portable and independent of the operating system it runs on.
virtual file system
The file system as the captured application sees it.
virtual registry
The registry as the captured application sees it.
vregtool.exe
A utility that compiles the virtual registry during the build process.