K, On holidays until midweek next week so I will have to get it to you then.
Thanks.
From: Neil Sleightholm [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n7587159...@n2.nabble.com]
Sent: Thursday, July 04, 2013 3:14 PM
To: Mark Van Dyke
Subject: Re: Burn - Localization Identi
OK, cool. Do I just send in the body of an email or attach a text file?
From: Neil Sleightholm [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n7587156...@n2.nabble.com]
Sent: 4 juillet 2013 12:55
To: Mark Van Dyke
Subject: Re: Burn - Localization Identifiers Duplicated
Feel fr
I am using 3.8.401.0. The problem has been fixed. It was unclear exactly how
to configure things but with the help of the forum and some trial and error the
solution has been found. It is in this thread (which has grown a little
lengthy). I will provide some updated documentation once Blair
PM
> To: Mark Van Dyke
> Subject: Re: Burn - Localization Identifiers Duplicated
>
> Ok, then what happens if you execute your bundle with "/lang 4105" passed on
> the command line?
>
> -Original Message-
> From: mvd1 [mailto:[hidden
> email]]
> Se
WiX) toolset]
[mailto:ml-node+s687559n7587099...@n2.nabble.com]
Sent: Tuesday, July 02, 2013 3:11 PM
To: Mark Van Dyke
Subject: Re: Burn - Localization Identifiers Duplicated
Ok, then what happens if you execute your bundle with "/lang 4105" passed on
the command line?
-Original Messag
older for 4105, 1033, 3084
and do they contain your localization files?)
-Original Message-
From: mvd1 [mailto:[hidden
email]]
Sent: Tuesday, July 02, 2013 3:52 PM
To: [hidden email]
Subject: Re: [WiX-users] Burn - Localization Identifiers Duplicated
Now it just errors with "The sys
riginal Message-
From: mvd1 [mailto:[hidden
email]]
Sent: Tuesday, July 02, 2013 1:34 PM
To: [hidden email]
Subject: Re: [WiX-users] Burn - Localization Identifiers Duplicated
.
.
.
When I change it to this, I get the following compilation er
hese files, then the next
release would probably have them by default.
-Original Message-
From: mvd1 [mailto:[hidden
email]]
Sent: Tuesday, July 02, 2013 12:33 PM
To: [hidden email]
Subject: Re: [WiX-users] Burn - Localization Identifiers Duplicated
The good news is that the correct .wxl files
, if you were willing to contribute these files, then the next
release would probably have them by default.
-Original Message-
From: mvd1 [mailto:[hidden
email]]
Sent: Tuesday, July 02, 2013 12:33 PM
To: [hidden email]
Subject: Re: [WiX-users] Burn - Localization Identifiers Duplicated
The
eq UX up, by chance is there a .ba or .ba2 folder. (I just thought of this
but the .Net UX may have its own folder to isolate it from possible file name
colisions.)
-----Original Message-
From: mvd1 [mailto:[hidden
email]]
Sent: Friday, June 28, 2013 3:27 PM
To: [hidden email]
Subject: Re: [
UX may have its own folder to isolate it from possible file name
colisions.)
-Original Message-
From: mvd1 [mailto:[hidden
email]]
Sent: Friday, June 28, 2013 3:27 PM
To: [hidden email]
Subject: Re: [WiX-users] Burn - Localization Identifiers Duplicated
I have tried these suggestions t
UX up, by chance is there a .ba or .ba2 folder. (I just thought of this
but the .Net UX may have its own folder to isolate it from possible file name
colisions.)
-Original Message-----
From: mvd1 [mailto:[hidden
email]]
Sent: Friday, June 28, 2013 3:27 PM
To: [hidden email]
Subject: Re: [WiX-u
I have tried these suggestions too and I have, again, tried variations on them
- all to no avail. Here is the current iteration:
I changed all my localization folders to be lowercase (en-us instead of en-US)
in case something in WiX was case-sens
OK, I have tried some different variations on Blair and Jacob's suggestions.
None have worked and there has been varying degrees of success. The most
successful correctly displayed the default Preqba.wxl entries that I have
defined (which are in English but my regional settings are fr-CA) but
I have verified that setting that WixVariable is what is controlling the
language that is displayed. If I switch to fr-CA Regional Settings but I have
English.wxl as the value of that variable, The .NET installer displays in
English. If I have en-US as my regional settings but I have French.wx
th\to\customlogo.png"
/>
...
Another ref: http://sourceforge.net/p/wix/bugs/2764/
I believe then burn will probe for the WXL based on the computers LCID, and if
it finds a localized version use it. If that fails, it should fall back to the
one in the root folder.
-Original Mes
Hey! Thanks! The compiler error is gone.
I was in the middle of putting together an example for this because what is out
there on this issue is very sparse and I haven't been able to find a
"start-to-finish" example. However, in putting all the pieces together, I
realized something and now I
Thanks for your reply to my issue. This sounds like something internal to
WiX. Is this something that I should be doing? From my meek understanding
of WiX though, what you are positing sounds like it could be the source of
the problem unless I am missing something.
Sorry for the delay in replyi
Sorry to confuse, The localization variables are just the ones defined in the
unmanaged bootstrapper that runs when a .NET 4.0 dependency exists (i.e.
.NET 4.0 is not present on the target system). I handle translations myself
in the Windows forms portion of the custom managed bootstrapper UI.
I
Let's forget about the Windows Forms portion. I apologize for throwing that
into the mix and confusing things.
What I am about to say only applies if a .NET dependency is detected and the UI
is displayed for that.
* I have been able to customize the .NET installation GUI using a .thm
That sounds reasonable. However, how do I do this? "Cultures to Build" is
disabled and I don't see any other spot to set this?
From: Nick Ramirez [via Windows Installer XML (WiX) toolset]
[mailto:ml-node+s687559n7586876...@n2.nabble.com]
Sent: Wednesday, June 26, 2013 11:56 AM
To: Mark Van Dyk
Shortly after I posted this yesterday, I figured out the problem. I am
trying to customize the built-in dialog for installing the .NET dependency.
>From my earlier post:
#(loc.InstallLicenseTerms)
#(loc.NetInstallAcceptAndInstallButton)
#(loc.NetInstallDeclineButton)
22 matches
Mail list logo
