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 InstallShield. Is there a Microsoft Merge Module specification document that I could point them to that would show them that they are producing broken merge modules? All the ICE validation tests appear to pass so I'm wondering how the WiX toolset can declare it's invalid. Bob Arnson-6 wrote: > > 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 warning go away? >> > > Don't use flawed merge modules. Otherwise, accept that you'll get a > warning. Suppress it if it's annoying. > > -- > sig://boB > http://joyofsetup.com/ > > > > ------------------------------------------------------------------------------ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://n2.nabble.com/LGHT1055-Warning-when-linking-2-InstallShield-merge-modules-tp3323234p3352085.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
