When you specify a value in the Help File Path setting, InstallShield adds a row for that custom action in the ISCustomActionReference table if one has not already been created. To resolve this validation error, open the Custom Actions view, select the custom action that is mentioned in the error message, and use the Help File Path setting to specify a path to the document that describes the behavior of the custom action. ISICE10 verifies that each custom action in your installation is documented by validating that each entry in the CustomAction table has a corresponding ISCustomActionReference table entry. This is especially helpful if system administrators deploy your product to enterprise environments they sometimes need to know what the custom actions do. The intended behavior of each custom action must be documented for the Windows Vista Quality Program. Here’s the information in the documentation about this validator: The errors about specific custom actions not being documented are validation errors for validator ISICE10. ISICE10 in particular reflects a particular method to document custom actions rather than the Logo goal of having them all documented.įrom user DebbieL, a Technical Writer at Installshield: Or, in short, if you run into a problem with a partiuclar ISICE validator, and your concern is acquiring the Vista Logo, it may be better to discuss it with those who run the Logo program. Just for your information, all of the validators named ISICE~~ are custom, and while they are designed to assist with passing the Vista Logo tests, I don’t believe that Microsoft considers our ISICEs to be authoritative. MichaelU gives his opinion on the relevance of such ISICE (Installshield Internal Consistency Evaluators) as it pertains to Window’s Logo testing: However, it doesn’t appear these ISICE errors will stop you from achieving Windows Logo Testing, so I consider them more of a warning/bestpractice.
Basically, you’re supposed to document what each custom action does in the ISCustomActionReference table. I found a few forum threads relating to Installshield’s ISICE10 validation errors I found interesting.
0 kommentar(er)
