ok thanks Sean! Good to know.
On Apr 12, 2015, at 7:59 PM, Sean Hall r.sean.h...@gmail.com wrote:
The Window text is set too early to do anything about it from
IBootstrapperBAFunction. You should localize that with a string in the wxl
file.
On Tue, Apr 7, 2015 at 2:17 PM, David Burson
The Window text is set too early to do anything about it from
IBootstrapperBAFunction. You should localize that with a string in the wxl
file.
On Tue, Apr 7, 2015 at 2:17 PM, David Burson david_bur...@ntm.org wrote:
In case it’s helpful to anyone, I posted how I got this working on SO:
In case it’s helpful to anyone, I posted how I got this working on SO:
http://stackoverflow.com/questions/29266905/wix-toolset-how-to-create-a-single-exe-with-product-name-localized-for-multiple/29499382#29499382
If anyone sees any improvements or problems, please post!
Thanks again for
OnDetectComplete handler is safe.
OnDetectBegin if you know that WixStdBALanguageId has been initialized prior
to OnDetectBegin.
--
View this message in context:
It works in OnDetectComplete!!! Thanks everyone for all the help. One
question though:
In my HyperlinkSidebarTheme wxl's, I use [WixBundleName] in several strings
(Caption, Title). If I use one of those strings in value of Window in my
HyperlinkSidebarTheme.xml, what is shown at install
Neither the wix39-debug.zip from https://wix.codeplex.com/releases/view/610859
nor the wix310-debug.zip from http://wixtoolset.org/releases/v3-10-0-1519/
included an SDK directory. Where does the SDK directory come from? What is
the proper way to get the source for 3.9 R2 and 3.10 so I can
When you install WiX, it creates the WIX environment variable which is used
in that sample project. It should point to the install directory,
typically C:\Program Files (x86)\WiX Toolset v3.10\. The header file
should be in the SDK\VS2010\inc directory in that install directory.
On Wed, Apr 1,
oops, last 2 lines should read:
hr = m_pEngine-SetVariableNumeric(L”WixBundleName, bundle_name);
BalExitOnFailure(hr, Failed to set WixBundleName variable.”);
On Apr 1, 2015, at 2:35 PM, David Burson
david_bur...@ntm.orgmailto:david_bur...@ntm.org wrote:
That was the problem - I had an old
That was the problem - I had an old version of WiX on my VS 2010 vm. I
installed 3.10 and the sample builds now.
If I understand correctly, to set the WixBundleName I need something like this
somewhere in BAFunctions.dll:
LPWSTR bundle_name = NULL;
switch (WixStdBALanguageId) {
case 1036:
Often the Programs Features contains the name of the product which is
typically a trademark (or treated like a brand in any case) and thus not
localized.
It's possible to change the name but wixstdba doesn't really expose it easily.
ok thanks Rob. That explains why I haven’t found an easy way to do this.
I’m trying to replace our old InstallAware installer with WiX. Generally I’m
much happier with what I have localized with WiX than with InstallAware.
However, with InstallAware we did localize the Program Features name
The sample is supposed to build with VS2010. IBootstrapperBAFunction.h
should be in the SDK directory with the other WiX header files like
dutil.h. Worst case scenario you can copy it from source at
https://github.com/wixtoolset/wix3/blob/develop/src/libs/balutil/inc/IBootstrapperBAFunction.h
.
Hi,
I’m trying to create my own BAFunctions.dll. All I want to do with it is set
WixBundleName based on the language of the user’s computer. Does something
like that already exist somewhere?
If not:
I’ve tried to build src\burn\Samples\bafunctions VS2013 and VS2010. Lots of
errors with
I don't know if changing WixBundleName at run time is a very good idea. I
never tried that. I would use the WixLocalization files to set strings
displayed to a user. See here
14 matches
Mail list logo
