Great. Thanks for pointing me to that information.
>From your comments, I am concluding the following:
1. Another ICE should be added to the standard set that at least validates
custom action names in merge modules to ensure they follow the naming rule.
(The fact that the error/warning does not
dmcgloin wrote:
> Are you saying that all InstallShield merge modules are invalid by default?
>
No.
> That would seem to be a serious bug in InstallShield. Is there a Microsoft
> Merge Module specification document that I could point them to that would
> show them that they are producing bro
Thanks, Bob. If possible, I would like some clarification on your comments.
In general, I like to have warnings as errors on our projects since it helps
avoid more serious issues.
Are you saying that all InstallShield merge modules are invalid by default?
That would seem to be a serious bug in
dmcgloin wrote:
> The WiX warning explanation seems to imply that the InstallShield default
> custom action is flawed, perhaps because the merge module custom action is
> not scoped to the Merge Module GUID in the ModuleInstallExecuteSequence?
>
> Is there a safe/recommended way to make this warnin
Use Orca from the Windows Installer 4.5 SDK and look for that custom
action in both of the InstallShield merge modules. I'll bet its in both
of those modules.
Check the resultant package build in Wix to make sure if you get one of
the copies of the functions.
Regards,
greenaj
On Fri, 2009-07-24
I'm getting the following warning when creating an MSI with 2 InstallShield
merge modules:
"warning LGHT1055 : The InstallUISequence table contains an action
'setAllUsersProfile2K' which cannot be merged from the merge module
'C:\Program Files\Company\SDK\Installation\Merge Modules\Spc5.0_Map.msm
6 matches
Mail list logo
