Hi Paul, > Admittedly, this is a completely different route from your "xml diff" > approach... would be useful though.
Indeed it would. However I'm not an XLST expert, and from my limited exposure that seems a more difficult option than using C#. Thinking out aloud... saute* [before] [after] [result.wxs] <options> Options: -u : generate uninstall create & delete commands as needed Pre-process: Parse both "before" and "after" into documents. i.e. validate is well-formed. Validate any schemas. Process (starting at root) 1. Look for "before" "after" attribute differences and generate commands if found. 2. For each child node in "before" Is the "after" file missing child node? Yes - generate delete commands and move to next sibling. 3. For each child node in "after" Is the "before" file missing child node? Yes - recursively create commands and move to next sibling. No - Start again from 1. on each grandchild node. i.e. recurse down tree. I appreciate recursion may not be the most efficient approach, but good enough for starters. Thoughts? * http://www.tfd.com/saute :) -- 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