> My guess is you need a <ComponentRef Id='EOD.xmlxml'/> > somewhere in your mymodule.wxs file to pull in the fragment > in your Templates.wxs file.
Okay. I'll try that. > What do you mean by " If I do the same thing to include them > in my main installer, it works fine."? You change <Module> > for <Product> and it works? Or what specifically do you do? I mean that if I don't include the fragment's file when I build my merge module, but I do specify it when I build the install, the installer installs it just fine. But that raises a point. I had to put ComponentRefs (or a ComponentGroupRef) in the main installer source to specify what Feature it goes under. So, it does make sense that adding the ComponentRefs to the merge source could do the trick. I'll try it and let you know. ---------- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
