How come you're using mst files for localization and not .wxl files that are
built into WiX?
http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/make_installer_localizable.html
--
View this message in context:
I suspect that wxl files were used to batch build the msi resulting in n msi
packages for n cultures defined. I used to do what I think he is doing,
using torch(or similar) to create mst files of the difference between my
base msi (english msi) and each of the other cultures, named :lcid.mst.
Thanks for the replies fellas. Phill is right on - that's the way I do it,
and because I inherited this project and am fearful of making big changes
and screwing it up ;-) it is still done this way. Someday I'll upgrade to
using Burn, too, and get off of the old Wix 3.5.
Now back to the
It looks like you have the .mst files because you are then embedding
into the MSI file. So you can open the base MSI file with Orca and use
the Transforms menu to apply them, the changes being highlighted. Do
you maybe no longer have the mst files or something?
---
Phil Wilson
On
Some more info:
http://stackoverflow.com/questions/16770848/how-to-read-msttransform-table-along-with-msi
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Embedded-Transforms-for-L10n-and-how-to-display-them-tp7598340p7598372.html
Sent from the
Thanks for the leads to the vb code - looks promising - and I do still have
the mst files to apply to the base msi using Orca - I was trying to figure
that out before - That helps a lot. I'm going to mess around with the VB
code for a bit.
--
View this message in context:
When I am done building my installer, (which includes a bunch of localization
stuff (which are .mst files embedded into the .msi file))
I'd like to know what the generated ProductCode's are for each .mst file
created in the build step. These files get merged into one .msi file, but I
cant see
7 matches
Mail list logo
