SparkleFlow is the acclaimed packaging solution that combines all aspects of a software packaging project into a single interface. Preparing an application migration? Need to reduce your TCO? Need to manage lots of applications? Want to setup your applications right now and not waste to much of your value time? SparkleFlow Package Management offers the complete solution for creating structure in your packaging project.
Written by Manfred van Poorten
Description:
ICE67 checks that the target of a non-advertised shortcut belongs to the same component as the shortcut itself, or that the attributes of the target component ensure that it does not change installation locations.
Failure to fix a warning or error reported by ICE67 can cause the shortcut to be invalid if the target component changes state and the source component does not. For example, when the target file's component is set to run from source, a reinstallation that changes the component to local results in the component containing the shortcut not being reinstalled. Thus the shortcut points to an invalid location.
Concerns:
ICE67 returns an error or a warning if the target of a non-advertised shortcut does not belong to the same component as the shortcut itself, or if the attributes of the target component do not ensure that the installation locations will not change.
Additional Information:
ICE67 verifies to see if a non-advertised shortcut refers to a file located in the same component. Unfortunately, it is quite often not possible to resolve this error as shortcuts are often placed in user-dependent directories. The component in which the shortcut is located must, as a result of this, hold a registry key under “HKEY_CURRENT_USER” as KeyPath. The file to which the Target is referring, is often machine-dependent. Because of this fact, this file is often KeyPath of the component in which this file is located.
It is not a problem if you decide not to resolve this error, however, you should make sure that both the component in the File and the component which hold the shortcut, are located in the same Feature. Naturally, the best solutution is to use solely advertised shortcuts!
Examples of possible errors:
File Table:
|
File |
Component_ |
FileName |
FileSize |
Version |
Language |
Attributes |
Sequence |
|
File1 |
Component1 |
|
|
|
|
|
1 |
Shortcut Table (partly):
|
Shortcut |
Directory_ |
Name |
Component_ |
Target |
Arguments |
|
Shortcut1 |
DesktopDir |
Application |
Component2 |
[#File1] |
|
Component Table:
|
Component |
ComponentId |
Directory_ |
Attributes |
Condition |
KeyPath |
|
Component1 |
{0F4....E7A0} |
INSTALLDIR |
2 |
|
File1 |
If you wish or must resolve this error:
1. Replace the shortcut by an advertised shortcut.
2. Place the shortcut in the same component as in File. (This creates a problem with per-user installation: other users won't get the shortcut!)
3. Place the file in the compoent in which the shortcut is located. (KeyPath is HKEY_CURRENT_USER registrykey, validation results in the error message “component contains both per-user and per machine components, with a per-user KeyPath”).
» Back to article overview