On 10/12/2009 17:10, Rob Mensching wrote: > Yes, there definitely is. Feel free to file a bug then use .wixlibs instead > of Merge Modules. <wink/> > >> On 09/12/2009 17:55, Wilson, Phil wrote: >>> All the CommonFilesFolder values in merge modules are by convention >> appended with a mangled guid, but as far as I can tell the mechanism that >> rationalizes all the folder name properties from merge modules (such as >> CommonFilesFolder.guid) at merge time is indiscriminate. If the folder name >> from the merge module *starts* with a standard folder property then the >> merge generates a CA to set it to the actual CommonFilesFolder. So when it >> gets merged into the MSI file it generates that type 51 custom action to set >> CommonFilesFolder<anything at all> to [CommonFilesFolder]. >>> >>> So yes, you're right, it is a really bad thing to use folder names in >> merge modules that start exactly like an actual folder name. >> >> Is there a case, then, for WiX giving a warning (or even an error) >> message if a Directory/@Id is used which starts with a predefined folder >> name?
Thanks, both, for your help. Bug submitted. I look forward to being able to use wixlibs, but for the moment at least I need retain compatibility with InstallShield :( -- Cheers, John ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
