Hi Karen,
We have a similar build routine here (use mallow to update
files/components, followed by candle and light) and decided to make the
jump to v3 some months back. I couldn't find a v3 replacement for
mallow, so I decided to try modifying it. Since it's (unobfuscated) .NET
code, it was easy to decompile using Reflector
<http://www.aisto.com/roeder/dotnet/>. I think I had to do a little
tweaking of the files to get them to compile, but can't remember the
details. After that, it the changes were pretty simple:
* change the namespace definition to
"http://schemas.microsoft.com/wix/2006/wi";
* change functions CreateDirectoryNode and CreateFileNode work with
the new schema (change "src" to "Source", get rid of the LongName
attribute
I'll see if I can get a go ahead from work to release my updated mallow.
Of course, all of the component rule warnings still apply, and I'm sure
anyone who really "gets" Windows Installer cringes whenever they see
folks talking about mallow and automatic component GUID generation. It
seems to be working for us for the past 3 years, so I guess we'll keep
on living dangerously :)
Don
kkmca wrote:
> I would like to convert my current installer from wix2 to wix 3 - installer
> is currently synchronized with mallow and then installer is built with light
> and candle using the ant dotnet task -
>
> what are some of the issues with moving to 3 from 2? will heat replace
> mallow effectively?
>
> Karen
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
