1. Agreed. It's been consistent feedback from me to the Windows Installer team that this is pain point. Admittedly, they've had bigger fish to fry.
2. Ahh, well, then that makes things easier. You don't need Merge Modules when installing to a private location. You just need to get the timestamps right to get the Windows Installer to behave correctly. Admittedly, icky. -----Original Message----- From: Scott Palmer [mailto:[EMAIL PROTECTED] Sent: Saturday, December 16, 2006 13:03 To: Rob Mensching Cc: wix-users@lists.sourceforge.net Subject: Re: RE: [WiX-users] Fwd: How can I force files to be overwritten? On 12/16/06, Rob Mensching <[EMAIL PROTECTED]> wrote: > > 1. It is buried somewhere. I think it may be around the File Versioning > topic. Got it.. very limited... makes installers hard to get right. The "rules" (i.e. "omus" vs "amus") should be per component. > 2. Shipping someone else's content to a shared location is a very dangerous > thing to do. I'm not installing to a shared location. > Are you using Merge Modules? No, the third party content is integrated directly into my installer. I just made a separate WiX source file for it and let the linker deal with it. Regards, Scott ------------------------------------------------------------------------- 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