Hello again, > And that's my only point -- nothing you mention requires dropping the > existing WiX CAs, just tweaks to them. XmlConfig, for example, is > definitely a low-level piece of functionality but it's entirely possible > to build higher-level extensions on top of it.
After chatting with Richard offlist, I'll go ahead and develop a .NET console app which compares two xml files and generates XmlFile/XmlConfig statements to produce a wxs file as the result. The app needs to ensure both xml files are well formed and schema compatible, and optionally provide uninstall statements as well as install statements. Can anyone think of anything else that would be useful to include? > But that's not going to happen unless we get focused feature requests > (e.g., "XmlConfig is hard to use for scenario Q for reasons A,B,C"). > One-off custom actions don't help anybody in the long run. Agreed. I'll post the source back to this list if I'm able to develop a usable tool. That will give WiX developers at least a starting point if they want to include in WiX itself. cheers si -- It's a wild world that we live in, you step to the vibe like a new found religion, take your position, compile your vision, futurism, algorithm has risen up! pfm - the western ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
