5.1

Example: Pointing to an Executable File of an Application
ThinApp can point the shortcut executable file AcroRd32.exe to the Adobe Reader 8.exe parameter, which is
the primary data container.
[AcroRd32.exe]
Shortcut=Adobe Reader 8.exe
Source=%ProgramFilesDir%\Adobe\Reader 8.0\Reader\AcroRd32.exe
ThinApp can point Microsoft Office Word 2007.exe, the shortcut executable file, to Microsoft Office
Enterprise 2007.dat, the primary data container file.
[Microsoft Office Word 2007.exe]
Source=%ProgramFilesDir%\Microsoft Office\Office12\WINWORD.EXE
Shortcut=Microsoft Office Enterprise 2007.dat
Shortcuts Parameter
The Shortcuts parameter lists the locations where the thinreg.exe utility creates a shortcut to a virtual
application.
The capture process determines Shortcuts entries based on the shortcuts the application installer
implements. MSI files use the Shortcuts parameter to determine the shortcuts to create.
Example: Modifying a Shortcuts Parameter
You can modify the Shortcuts parameter to create a shortcut in the Microsoft Office folder of the Start menu
to the Microsoft Word 2003 application. If you add shortcut locations, use semicolons to separate the entries.
Each entry can contain folder macros.
[Microsoft Office Word 2003.exe]
ReadOnlyData=bin\Package.ro.tvr
Source=%ProgramFilesDir%\Microsoft Office\OFFICE11\WINWORD.EXE
Shortcuts=%Programs%\Microsoft Office
Source Parameter
The Source parameter specifies the executable file that ThinApp loads when you use a shortcut executable
file. The parameter provides the path to the executable file in the virtual or physical file system.
ThinApp specifies the source for each executable file. If an application suite has three user entry points, such
as Winword.exe, Powerpnt.exe, and Excel.exe, the Package.ini file lists three application entries. Each entry
has a unique source entry.
If ThinApp cannot find the source executable file in the virtual file system, ThinApp searches the physical
file system. For example, if you use native Internet Explorer from the virtual environment, ThinApp loads
the source executable file from the physical file system.
The Source and the /bin directory in the project are not related to each other. The /bin directory stores the
generated executable file and the Source path points to the installed executable file stored in the read-only
virtual file system.
NOTE Do not modify the Source path. The capture process determines the path based on where the
application installer places the executable file in the physical file system of the capture machine. ThinApp
creates a virtual file system path based on the physical file system path.
Chapter 17 Configuring Individual Applications
VMware, Inc. 59