Reply to Message

View discussion in a popup

Replying to:
TobyFruthParson
Enthusiast
Enthusiast

There are a few icon considerations to be made within ThinApp.

There's the icon folks will see in the "Add/Remove Programs" or "Programs & Features" list.  This is known as the

MSIArpProductIcon

and an entry for it should appear in the MSI portion of Package.INI.

There's the icon someone might see when working with software inventory.  This is known as the

InventoryIcon

and an entry for it should appear in the General Purpose Parameters portion of Package.INI, just below the SandboxName.

Then there's the entry points.  Assuming your virtualized Word is the only Word on the system, and assuming that there's only one entry point for winword.exe in your Package.INI, then you should expect to see the correct icon.

Using an example from one of our Acrobat captures, here's the Package.INI entry for Adobe LiveCycle Designer 8:

[Adobe LiveCycle Designer 8.0.exe]
Source=%ProgramFilesDir%\Adobe\Acrobat 8.0\Designer 8.0\FormDesigner.exe
Shortcut=Adobe Acrobat 8.2.6 Professional.dat
Icon=%ProgramFilesDir%\Adobe\Acrobat 8.0\Designer 8.0\FormDesigner.exe
FileTypes=.tds
ObjectTypes=

Shortcuts=%Programs%\Adobe

On some occasions, I have noticed that an application has two entry points in Package.INI, one that is enabled and another that is disabled.  If you are like me, you delete the %SystemRoot%\Installer directories from your packages prior to build.  Do you also, like me, occasionally forget to delete the %SystemRoot%\Installer entries in Package.INI?  I have done so in times past, and the result is, despite the fact the file is not in the project folder and the entry point is disabled, Package.INI makes a reference to a non-existent file.  Perhaps this is the root cause of the icon issue.  You see, sometimes, the Icon= entry points to a %SystemRoot%\Installer entry, rather than directly at the installed application EXE.

Toby Fruth, Sr. Specialist, The Parsons Corporation
Reply
0 Kudos