1. Yes, absolutely. Burn supports parsing the "standard package switches"
and will pass extra switches on the Bootstrapper Application so it can apply
additional behavior.
2. The complete list is dependent on the Bootstrapper Application you pick.
The wixstdba supports only the "standard package s
Again, Burn is more about creating a unified installation experience than
displaying a "collection of random installation experiences". I suggest
playing with Burn and seeing how it caches content for you then executes the
installs to better understand the flow and why I'm challenging the
assumptio
I've seen it work fine with both Traditional and Modern sort LCIDs (for
Spanish, anyway). In fact, for all the ones I tested (back on Server 2003,
XP, and Vista, anyway) all the Spanish LCIDs I tested (including neutral)
worked.
Neutral Chinese comes out backwards between NLS and .NET (traditional
Hi everyone,
Is it possible to run Burn-driven installer in a quiet mode? What command line
parameters are supported? Can I forward any parameter/property to chained
package(s) via bootstrapper command line?
Thanks in advance.
--
Vitalii Dolia
--
Rob Mensching robmensching.com> writes:
> Maybe. It's not really in the model Burn was designed for. Burn was intended
> to provide a seamless installation experience not pop up a bunch of
> different installation wizards.
[skipped]
> Burn is designed to provide
> the antithesis of that experienc
For spanish I think it is traditional sort 1034, or at least it works
with that LCID
2011/1/11 Tobias S :
> You will find a list with the needed LCIDs e.g. here
> http://technet.microsoft.com/en-us/library/dd744369%28WS.10%29.aspx ->
> Language Packs
>
>
>
> 2011/1/11 :
>> Hi All,
>> I'd like to
LCID values are not automatically transferred from the culture's name to the
different places in the MSI database where it may be needed. There are some
LCID values defined in .NET that don't work on all platforms (and even a
couple places where the LCID in native code and the value used in .NET do
You will find a list with the needed LCIDs e.g. here
http://technet.microsoft.com/en-us/library/dd744369%28WS.10%29.aspx ->
Language Packs
2011/1/11 :
> Hi All,
> I'd like to clarify LCIDs of the supported languages of WixUIExtension.
>
> Table of LCIDs from MSDN
> (http://msdn.microsoft.com/e
IMHO: best practice in Windows Installer is in this order:
1. Find a way to accomplish what you need to do using standard (built-in)
actions (see Bob's "semi-custom" actions if you need to compute things like
registry keys, etc. at install-time).
2. Use a well-written, well-tested, and well-used li
Option #1: make A.DLL "delay load" B.DLL and also load B.DLL into a resource
in A.DLL. Either from your DllMain() method or from your custom action
method(s), extract B.DLL from its resources into the same directory as the
A.DLL was extracted to by Windows Installer. Erase it in DllMain() when the
OK, I found the problem: I copy/pasted the code into a new sample and
forgot to change the GUID :( Once I use a unique GUID everything works fine.
MeCoco
On 1/10/2011 6:02 PM, MeCoco wrote:
> Hi all,
>
> I wrote the needed code to create 2 shortcuts: one in the Start Menu and
> the other one on
Hi All,
I'd like to clarify LCIDs of the supported languages of WixUIExtension.
Table of LCIDs from MSDN
(http://msdn.microsoft.com/en-us/library/0h88fahh(v=vs.85).aspx):
Locale description Short string Hexadecimal value Dec
Hi All,
I'd like to clarify LCIDs of the supported languages of WixUIExtension.
Table of LCIDs from MSDN
(http://msdn.microsoft.com/en-us/library/0h88fahh(v=vs.85).aspx):
Locale description
Short string
Hexadecimal value
Decimal value
...
...
...
...
Chinese - China
zh-cn
0x0804
2052
13 matches
Mail list logo
