Novell ADMINSTUDIO 9.5 User Manual page 654

Chapter 9: Converting Windows Installer Packages to Virtual Applications
About ThinApp Virtual Packages
Table 9-5 • Components of a ThinApp Application
Number of
Shortcuts
More than 1
shortcut
Metadata File
Caution •
ThinApp Assistant.
Intermediate Data Files: Interm Directory
When a ThinApp application is built, files that support the ThinApp application build process are extracted out of
the Windows Installer package and saved in a subdirectory of the
directory.
Figure 9-7: Interm Subdirectory of the ThinAppPackage Directory
The data in this directory is then compiled into ThinApp application as part of the build process. The data in the
directory does not need to be distributed with the ThinApp application.
Interm
654
ThinApp Application
Components
ProductName.exe
FeatureName.exe
Package.DAT
metadata.xml
Modifying these files directly is not recommended. To make any modifications, use the InstallShield
Description
The ThinApp application consists of two or more
executable files and a
Package.DAT
• Launching the application—Each of the
executables is used to launch the ThinApp
application or a specific feature of the ThinApp
application.
•
Location of application
file contains all of the files, registry
Package.DAT
keys, DLLs, ThinApp components, and third party
libraries that are required for the application to
run.
An XML file created during AdminStudio 9.0+ package
conversion that contains metadata identifying the
original Windows Installer package that was used to
create the virtual package.
Note • Because of this file, you are able to import this virtual
package into the Application Catalog and associate it with its
source Windows Installer package. For more information, see
Importing Virtual Packages.
directory named the
ThinAppPackage
ADS-0950-UG00
file:
data—The
Interm
AdminStudio 9.5 User Guide