Cool, thanks. If worst comes to worst, I'll just fire up Process Monitor
again and watch the file system activity to see what files the bootstrapper
is looking for (and not finding.)
Somehow, that feels more fun than wading through source code.
Alnoor
--
View this message in context:
http://w
Hi Phil,
Glad to help, and thanks for the suggestions. It does make sense to localize
the theme itself, though I have not done so yet. Did you try it?
Alnoor
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experiences-making-a-multi-language-b
Hi again,
One further detail: Note the theme in the payload is named 'thm.wxl'. This
is important! The bootstrapper only uses translations if they are in a file
with this name.
Alnoor
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/My-experienc
Hi Tim,
My original question was a little bit misguided -- there are no translations
for the RtfLicense theme included with WiX 3.7. The translations are for a
different them called mbapreq, which doesn't seem to have a license dialog.
In the interest of saving someone a few minutes (perhaps me,
Hi,
Great post! How does this change in WiX 3.7?
I downloaded the WiX 3.7 source and noticed that the wixstdba folder now
contains localized resources for a number of languages.
When creating a bundle: Is there a shortcut to reference these localized
themes, or do I have to copy them to my own
Cool. So we have a Burn variable called SqlCe40Version, that contains a
version string like "14.0.0.0"
How can we do a version comparison with a hardcoded string, like
"v4.0.8876.1"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/SQL-CE-4-0-Packag
6 matches
Mail list logo
