On 10/5/06, Mike Dimmick <[EMAIL PROTECTED]> wrote: > 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.
Mike, Thanks for the reply. Yes, It was initially obvious that the wix linker resolves references befor merging the MSM. I don't know if this is the right thing to do in this case. > 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. Ok, thanks for this recommendations. > 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? Unfortuantely all of my installers are not authored using wix. The MSM comes from a third party who prodives drivers through the MSM. More and more driver vendors are providing their files as MSM's, which is nice, but often the MSM's are broken by design. 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=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
