Sean,
Creating the actual extensions to the compiler (candle), linker (light),
decompiler (dark), serializer / gatherer (heat), etc. requires a .NET
assembly; your choices there include managed C++ or a managed wrapper
around a native DLL.
That said, most of the extensions are coupled with Cus
is.
> Cheers
> Sean.
>
>
> -Original Message-
> From: Bob Arnson [mailto:b...@joyofsetup.com]
> Sent: 19 February 2009 18:01
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] creating wix extensions
>
> Sean Farrow wrote:
etup.com]
Sent: 19 February 2009 18:01
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] creating wix extensions
Sean Farrow wrote:
> Firstly, thanks for the pointers. How then do I fill a table using a
> custom action at runtime. It seems I can get away
Sean Farrow wrote:
> Firstly, thanks for the pointers. How then do I fill a table using a
> custom action at runtime. It seems I can get away with doing this, and
> then have in installation query this table for the info I need via other
> ca's.
>
If it's static data, it'll be much easier to cr
ogers [mailto:rogers.br...@gmail.com]
Sent: 18 February 2009 22:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] creating wix extensions
Hey Sean,
WIX extensions are based in managed code (.net). You could use managed
C++ to develop the extension, but not native code.
Hey Sean,
WIX extensions are based in managed code (.net). You could use managed C++
to develop the extension, but not native code. I am curious how you are
comparing a custom action to a WIX extension. An extension, typically, is
used to modify the input .wxs file to the output .wixobj file and t
6 matches
Mail list logo
