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).
To use external cab files it seems like I need to figure out how to change the msi package name, as a part of the MSBuild batched culture build, so that all msi packages and the external cab can coexist in the same folder (or subfolders). I assume that the package name needs to be changed in the batched build process, based on reports of problems from changing the name of the package after it was built, unless I misunderstood those reports. So based on those concerns I was evaluating writing some MSBuild targets to intercept the paths that WixAssingCultures, etc creates and trying to also modify the file name with the culture string (ie TargetPath <somepath>\culture\MyMsi_culture.msi;<somepath>\anotherCulture\MyMsi_anotherCulture.msi I'm sure that I have overlooked something, so I appreciate any feedback. Thanks. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-external-cab-for-multiple-language-msi-packages-tp7596991.html Sent from the wix-users mailing list archive at Nabble.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
