Hi Richard, > These all seem like very reasonable feature requests for WiX as an > extension/adjunct to the existing XmlConfig actions.
Agreed. We'd prefer not have to code this ourselves and worry about custom actions. > I'm assuming that the XmlTidy action is only because when WiX edits an > XML file, it does unwanted things to the whitespace in the XML file? Correct. On installs it can create elements without adding a CRLF to the parent element. On uninstalls it doesn't remove CRLF from deleted elements. So I end up using Visual Studio "Format Document" command (Ctrl+E, D) quite often when testing. This fixes the first problem (for testing, not for deployment) but not the later. > I'd treat that more as a bug to XmlConfig/XmlFile. Agreed, although I posted to this list recently about this - subject heading "Xml Beautifier" - and it didn't elicit much response so I didn't bother filing an issue. Perhaps it was poorly written. > What about this: would you be happy with a tool that took two XML > files, a "before" and "after" version, and processed the differences > to generate the appropriate XmlConfig/XmlFile nodes? Yes, that's an excellent idea! The "before" file wouldn't have to be the whole configuration file, just the elements and attributes needed for the xpath queries. > That could be part of your build process so that ongoing iterative > changes could be incorporated automatically. Sounds good, and thanks for your input. Shall I go ahead and create a feature request for this tool? cheers si ------------------------------------------------------------------------- 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
