Ok Phill, I was able to download and extract the files from your zip. I tried
out both .exe that you created and created a German VM to test on. They did
show the German EULA and when I switched to my French image it showed the
English EULA.
I then updated your German .wxl file with German text
No, but I had a similar issue and determined that Symantec is assuming that
if the package does not have a valid Code Signing signature it is a virus.
There is no virus, it is a FALSE Positive which many others have also had
issues with. If you use your code signing certificate to sign the
Placing the WiXBalExtentionExt.dll file into my WiX 3.7 bin folder did not
make a difference. So was there anything else you had to do or did to make
this work?
Can both 3.7 and 3.8 reside on the machine at the same time? If as you said
that 3.8 already has the fix in it then I was thinking of
After doing this experiment with your code and demonstrating that
automatically detecting languages works using WiX 3.7, even without
specifically using the WiXExtenededBootstraperApplication, I switched my
main project (seven languages) back to Wix 3.7. I did limited testing on my
Windows 8 test
Okay after getting your install to build I test and it will still not show
German or French licenses on German and French systems. This is still
building with WiX 3.7 and having the updated WiXBalExtentionExt.dll file
into my WiX 3.7 bin folder.
So just having no luck what so ever.
I'll look at
Well, I am sorry to hear that it is not working for you. Since I can build
it with 3.7 and it works, I think I would try to use ProcessMon or WinDbg to
figure out what the issue is, focusing only on the German Wix 3.7 exe which
I complied for you and your compilation of the same thing.
Okay, when I installed the latest WiX 3.8 and Updated my project files to use
3.8 the build correctly built in the UI so that on German the UI/EULA is
German, on French it is French and on English and unsupported languages it
shows English.
So yes 3.8 has the fixes in it. So my version of 3.7 has
When I added the WixExtendedBootstraperApplication to my Wix 3.7.1224
installation, I downloaded the zip package from:
http://wixextba.codeplex.com/releases/view/105895
And I put the one DLL in that package into my Wix Toolset 3.7.1224\bin
folder.
At a later point I did what I described in
Tim; I took your wxs file and added it to a new WiX bootstrapper setup
project (in VS2010). I tried to recreated your file tree as closely as
possible and I stripped out the code that was not related to testing whether
the localized files were displayed, without needing to provide the -lang
Attached is my main WiX Burn .wxs file:
TableToolkitBootStrapper.wxs
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/file/n7588120/TableToolkitBootStrapper.wxs
Now again this will correctly add the .mst files and push the correct .mst
file on the command line to the .msi as long
Here is my code:
lt;BootstrapperApplicationRef
Id=WixStandardBootstrapperApplication.HyperlinkLargeLicense
lt;bal:WixStandardBootstrapperApplication
LicenseUrl=http://www.company.com/license.html;
LocalizationFile=Resources\QDthm.wxl
ThemeFile=Resources\QDthm.xml
Thanks Neil...
Phill you mentioned the following:
Phill Hogland wrote
I looked at your code. You do not have any translated Payload .wxl files
with name attributes in the form LCID\thm.wxl , etc.
And I do have translated Payload .wxl files, they are listed in the
PayloadGroup
Tim, I'm sorry. You are correct that I did not read down far enough.
I looked it over more carefully and I do not see a problem with your code.
I guess I would study a ProcessMon log or setup WinDbg.
--
View this message in context:
Brian,
I currently already have English MSI and supported language .mst's in my
Burn Wrapper .exe. I generated the language .mst in my VS 2010 project by
running the PostBuildEvent Torch.exe -t language command on each of the
language .msi file compared against the English .msi.
So the Burn
Okay I have not yet figured this out. I have tried placing the calling of my
MsiPackage into a separate Fragment file and add a property definition to
default language and then conditioned custom actions for the supportted
languages, but it looks like Burn completely ignores this default property
Burn and its existing WixStdBA don't support this out of the box today. I see
two choices for you. The first is to have a single msi with no transforms and
either use multiple components with conditions on the localized shortcuts or
utilize a CA at runtime to inject the localized shortcuts
Okay thanks Jacob...
So figuring I would go with the easiest method I started to convert my main
project with conditioned language components and then when I build I then
receivce a bunch of errors stating:
error LGHT0311: A string was provided with characters that are not available
in the
[mailto:timmay...@smarttech.com]
Sent: Monday, July 08, 2013 12:01 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?
Okay thanks Jacob...
So figuring I would go with the easiest method I started to convert my main
project
Okay thanks Jacob...
After a bit more testing I was able to get this to work by using the
InstallCondition. When I first tried using the InstallCondition I was
looking for languages like this:
InstallCondition=[SystemLanguageID]=1036 and this was failing.
After some research I found out that I
[mailto:timmay...@smarttech.com]
Sent: Monday, July 08, 2013 4:34 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?
Okay thanks Jacob...
After a bit more testing I was able to get this to work by using the
InstallCondition. When I first
There should not be a problem with Product Codes as I am using the same .msi
in both MsiPackage entries, not multiple msi's that are language specific.
I have again just the one .msi and the language .mst's files. So if one of
the supported languages exists it will trigger the first MsiPackage ID
Okay thanks, that is something I'll have to look at...
Now as for my error when running on a OS that is running a different
language than what I support. Is there any examples that you can direct me
to that would help me to create a custom action to condition the TRANSFORMS
property so that if
Thanks Jacob,
So added all the supported language .mst's using the Payload element under
the MsiPackage, but without being able to condition if one of the supported
.mst's are to be used or to have to use the default languages of English
then again it makes it harder to use.
So it looks like
Okay adding all supported language .mst's by Payload element and then having:
MsiProperty Name=TRANSFORMS Value=[SystemLanguageID].mst /
Does work. The install did install the shortcuts under the correct language,
but if you are running on a unsupported language, a language that we do not
have a
if you're interested in
contributing.
Date: Wed, 3 Jul 2013 14:54:38 -0700
From: timmay...@smarttech.com
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Adding language transform .mst's to Burn Bundle
Chain?
Okay adding all supported language .mst's by Payload element
...@smarttech.com]
Sent: Friday, June 28, 2013 12:46 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Adding language transform .mst's to Burn Bundle Chain?
I am creating my first bootstrapper .exe that installs some prerequisites .exe
and then triggers my WiX .msi installer.
This all
26 matches
Mail list logo
