Phill Hogland wrote
> 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.
Bob;
I am currently using in each MSI project the following:
<CabinetCachePath>cabs</CabinetCachePath>
<ReuseCabinetCache>True</ReuseCabinetCache>
along with:
<MediaTemplate EmbedCab="yes" />
If I change to external cabs then does you comment imply that I should use
Media/@Layout to specify the "common directory"?
Currently the folder tree is:
culture1\mymsi.msi
culture2\mymsi.msi
I assumed, maybe incorrectly, that if I use a external cab it would have to
be in the folder that the msi is in, which would still not work unless there
was some way to change the name of the various msi(s) which all use the
common external cab. I am also under the impression that renaming the msi
after it is compiled causes problem. Is that incorrect? I'm interested in
doing it the way you would do it, but I am not sure where to set the common
directory and let targets do it's thing.
The second approach does not seem viable but right now I am trying to
understand the first approach.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-external-cab-for-multiple-language-msi-packages-tp7596991p7597126.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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
