Thanks. You confirmed my memory.
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Jeremy Farrell [mailto:jeremy.farr...@oracle.com]
Sent: Friday, June 13, 2014
Did fallback not help?
http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/specifying_cultures_to_build.html
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original
That sounds a lot like:
In addition to Melt.exe supporting an input of a merge module and an output of
a WiX source file, I added a new mode: inputs of the .msi and its matching
.wixpdb files and as output, the directory where the .msi contents are
extracted and a new .wixpdb that's a copy of
How would that commandline be for that case?
If you have wxl files for both languages I kinda understand it, but here I
was including the IisExtension, and using nb-NO cultures which it did not
contain, If I then had to get the english wxl to make it to fallback to
that, I'm kinda just as far.
But
On 6/14/2014 3:02 AM, Rob Mensching wrote:
That sounds a lot like:
Yep. If it's not working, it could be a bug in Melt.
--
sig://boB
http://joyofsetup.com/
--
HPCC Systems Open Source Big Data Platform from LexisNexis
5 matches
Mail list logo
