On 25-Sep-14 13:24, Phill Hogland wrote: > Using a Burn driven MSIs, without using language transforms, results in MSI > packages, of the same name, in a culture named folder tree. I have also > been evaluating using external cabs for the common files. From what I have > reviewed the cab gets created in the MSI output folder (or subfolder below > the culture named parent folder). I'd do it this way: Set cab cache path to a common directory then let wix.targets do its thing. Then assemble a new image you use to build the bundle from.
Alternately, don't use the Cultures support to build multiple .msis in one go. I typically build one language at a time. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
