Edytuj

Udostępnij za pośrednictwem

ICE59

  • Artykuł

ICE59 checks that advertised shortcuts belong to components that are installed by the target feature of the shortcut.

Errors reported by ICE59 generally lead to the following behavior:

  1. The advertised shortcut will launch the Windows Installer to install the feature listed in the Target column.
  2. But because the FeatureComponents table does not map the target feature to the component containing the shortcut, the keyfile of the component (which is activated by the shortcut) is not installed.
  3. Therefore the shortcut is broken and will not do anything.

Result

ICE59 posts an error if an advertised shortcut does not belong to the components that are installed by the target feature of the shortcut.

Example

ICE59 reports the following error for the example shown:

The shortcut ShortcutB activates component ComponentB and advertises feature FeatureA, but there is no mapping between FeatureA and ComponentB in the FeatureComponents table.

In this case, ShortcutB advertises FeatureA, and when activated, starts the key file of ComponentB. Yet ComponentB is never installed by FeatureA, so even after the installation-on-demand phase completes, the target of the shortcut does not exist.

To fix this error, add a row to the FeatureComponents table that associates FeatureA and ComponentB.

Shortcut Table (partial)

Shortcut Target Component_
ShortcutB FeatureA ComponentB

 

FeatureComponents Table

Feature_ Component_
FeatureA ComponentA

 

Feature Table (partial)

Feature Level
FeatureA 10

 

Component Table (partial)

Component KeyPath
ComponentA FileA
ComponentB FileB

 

File Table (partial)

File Component_ Sequence
FileA ComponentA 1
FileB ComponentB 2

 

ICE Reference