Actually, your suggestion about using Fragments is a very much recommended. Merge Modules should be used when you are distributing blocks of code to across organizations that don't all use the WiX toolset. Otherwise, .wixlibs are far more efficient and powerful.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick Sent: Thursday, October 05, 2006 8:04 AM To: Carlos O'Donell; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Calling a CustomAction defined in an MSM. I think it's simply that all the references are resolved by the linker _before_ the MSMs are merged in. This makes it impossible to reference anything in the MSM. I think merge module custom actions should be scheduled by authoring them in the ModuleInstallExecuteSequence (or ModuleInstallUISequence) table. Merging the module then places the custom action in the right relative place in the corresponding Install sequence. I'm not sure how to do this with WiX - it's possible that including the <InstallExecuteSequence> in a <Module> will do the right thing. If all your installers are using WiX, and you wrote this merge module, it seems to me that you might get better results by simply referencing WiX <Fragment>s. If you have a lot of <Fragment>s and you want to save the compile time, you could use lit.exe to make a .wixlib from the resulting .wixobj files. Anyone know better? -- Mike Dimmick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos O'Donell Sent: 02 October 2006 20:59 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Calling a CustomAction defined in an MSM. WiX Users, I have an MSM that defines a set of "CustomAction" entries. The MSM is merged into the MSI, and it is my responsibility to execute the MSM's custom actions. Unfortunately when I compile my project, light rightly complains: C:\xxx\yyy.xml : error LGHT0112 : Unresolved reference to symbol 'CustomAction:foo' in section 'Product:12345678-1234-1234-1234-123456789012'. It would seem that the CutomAction's in an MSM are not available from the MSI? It is essentially this issue: [ 1541952 ] Unresolved Reference error when using CA declared in MSM The original response seems to be: "You cannot create references from products into merge modules." Why is this the case? Is someone able to clarify why products can't reference or call custom actions in merge modules? Any guidance is much appreciated. Cheers, Carlos. ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE V _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
