It does work. Just had to use the *#*(loc.StringId) instead of the
*!*(loc.StringId) syntax for the bal:Condition@Message attribute. The
WixStdBA localizes with the # syntax.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localizing-Burn-Condition
I am using the WixStdBA and have got it (mostly) localized by following the
'Payload Name=LCID\thm.wxl' approach described at
https://classicwixburntheme.codeplex.com/.
However, I'm having an issue getting the bal:Condition element messages
localized accordingly. They always display in English, ev
Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit
>>>> > msiexec.exe
>>>> for a 64-bit MsiPackage
>>>> >
>>>> > What is the bitness of your CA DLL? Just a stab in the dark but
>>>> > you
>>>> might need to have it compiled twice, once as 32 and once as 64,
>>>> and
://www.firegiant.com/
-Original Message-
From: Ryan Waller [mailto:rwal...@microsoft.com]
Sent: Friday, November 14, 2014 7:43 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a
64-bit MsiPackage
Yes, Orca Summary
Yes, Orca Summary shows it with Platform x64.
-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Friday, November 14, 2014 6:33 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] [SPAM] Re: WixStdBA launches 32-bit msiexec.exe for a
64-bit MsiPackage
When
I'm using the WixStdBA to conditionally install either a 32-bit or a 64-bit
MsiPackage.
When my 64-bit package is installed a 32-bit version of msiexec.exe is launched.
Is there way to force the 64-bit msiexec.exe to get launched?
My MSI has a custom action to check for a running process and v
refers to Font elements (
http://wixtoolset.org/documentation/manual/v3/xsd/thmutil/font.html)
created in your theme file.
On Thu, Nov 6, 2014 at 8:22 PM, Ryan Waller wrote:
> Where can I find a list of the supported FontIds and their
> descriptions, for use with Theme elements used
Where can I find a list of the supported FontIds and their descriptions, for
use with Theme elements used in the RTFTheme.xml in WixStdBA?
For example, I'd like to change the FontID of the Text element to Bold, and
maybe even Orange color.
http://wixtoolset.org/documentation/manual/v3/xsd/thmut
vated
WixStdBA handles this without a CA via:
-Original Message-
From: Ryan Waller [mailto:rwal...@microsoft.com]
Sent: Monday, November 03, 2014 4:32 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Bootstrapper runs msiexec elevated which causes my MSI
CustomAction to run ele
I've authored an MSI package that uses a CustomAction to launch an application
after install completes. The package requires elevation but the CustomAction is
scheduled after InstallFinalize to launch the application as the Standard User,
not elevated.
When installing the MSI alone using msie
10 matches
Mail list logo
