"Have you looked at dark (the WiX toolset decompiler)? Dark v3 is particularly solid. It will drop all of the files and .wxs authoring in such a way that the compiler and linker can put it all back together."
This implied an IJW symbiosis between Dark and Candle and it simply isn't true. Instead of acknowledging that YMMV in the `real world`, the MSM to be decompiled is characterized as `poor authoring`.
Here is another example. I have a collection 70 MergeModules ( that ALL pass validation ). Each module implements one or many AppSearch patterns. Dark fails to extract the PID_REVNUMBER out of the Summary Information stream on nearly 40% of them. When I try to candle them they fail since they don't have a valid identifier. If I look at the summary info in Orca they are fine. If I export and import using MSI2XML its fine. If I merge the modules into an installer it's fine.
I've really tried to open the door and fit WiX into my existing installer solution but I just got tired of banging my head against the wall trying to make it work. MSI2XML and MSIDB worked just fine without any effort and I wanted to let Simon know what to expect.
Derek Cicerone <[EMAIL PROTECTED]> wrote:
Christopher,I'm sorry, but I think its a particularly unfair comment to say that a bug in dark was "scoffed to the side". I believe the particular issue you are referring to dealt with dark creating output that when compiled immediately produced errors. I would like to explain why that was done.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
