In article <[EMAIL PROTECTED]>,
si <[EMAIL PROTECTED]> writes:
> What I'd like is something as simple as the XmlPoke and XmlPeek tasks
> that are found in NAnt. [...]
> We'd also like an XmlBulkAdd action i.e.
> adding well-formed elements and attributes instead of having to treat
> each element value or attribute invidually. With those actions I
> could get my wxs file mentioned above down to less than 100 lines,
> making it easier to develop, understand, test and maintain.
>
> We'd also write an XmlTidy action [...]
These all seem like very reasonable feature requests for WiX as an
extension/adjunct to the existing XmlConfig 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?
I'd treat that more as a bug to XmlConfig/XmlFile.
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?
That could be part of your build process so that ongoing iterative
changes could be incorporated automatically.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
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
