Reply to Message

View discussion in a popup

Replying to:
TobyFruthParson
Enthusiast
Enthusiast

My two cents:

From page 48 of the ThinApp 4.7 manual PDF:

Update Firefox 2.0.0.3 to Firefox 3

1. Capture Firefox 2.0.0.3 and Firefox 3 into separate packages.

2. Verify that the primary data container name is the same for both packages.  The primary data container, determined during the setup capture process, is the file that contains the virtual file system and virtual registry. If you have a Firefox 2.0.0.3 package that has Mozilla Firefox 2.0.0.3.exe as the name of the primary data container, and you have a Firefox 3 package that has Mozilla Firefox 3.dat as the name of the primary data container, change the name in the Shortcut parameter to a common name. For example, you can use Firefox.exe as a name.

From page 49:

Maintaining the Primary Data Container Name with Application Sync

The Application Sync utility requires that the name of the primary data container, the file that stores virtual files and registry information, is the same for the old and new versions of an application. For example, you cannot have an old version with Microsoft Office Excel 2003.exe as the primary data container name while the new version has Microsoft Office 2007.dat as the primary data container name. To verify the name of the primary data container, see the ReadOnlyData parameter in the Package.ini file. For more information about the primary data container, see “Defining Entry Points as Shortcuts into the Virtual Environment” on page 15.

From personal experience:  searching VMware's site for "Optional" or "RequiredAppLinks", you will find threads and posts stating you must use a DAT file for AppLink functionality to work.  I recommend using DAT files.  Seems to me they are nedded more often than not, so I always create a DAT file.

Toby Fruth, Sr. Specialist, The Parsons Corporation