Integration into the DSM environment

ThinApp is entirely integrated into the DSM environment. The virtual application wizard enables you to both generate new virtual applications, and package existing virtual applications for subsequent distribution to installation targets.

For ThinApp applications there is a separate software package called the ThinApp package. Here the parameters to generate a ThinApp application are saved as ThinApp shortcuts and installation parameters and thus virtualized. In each build process a package.ini is generated from these parameters. The package.ini itself drives the ThinApp build process.

If you do not enter a path to the sandbox, the ThinApp standard path is used as a default (%appdata%). An eScript command InstallThinAppPackage is generated in the course of virtualizing an application. This script is responsible for installing the virtual application on managed computers. The script can be adapted and expanded.

The InstallThinAppPackage command is part of every ThinApp application package. It points to a virtual application in a package directory. With each build process of ThinApp tools the name of this package directory alters, and with it the InstallThinAppPackage command. A build process is triggered for example by the task generate ThinApp package again, or the task prepare distribution. So you can only insert your own commands in the ThinApp application package after the InstallThinAppPackage command.

The files required to build a virtual application with the ThinApp Tools (ThinApp source files) shall not be distributet together with the software packages to the managed computers. It is sufficient for the virtual application as the result of the ThinApp build process to be distributed. Thus the ThinApp source files are saved in the special folder \intern$, which is a subfolder of the package folder. Files in the \intern$ folder will never be distributed.