The xmlpeek and poke tasks could be very useful for a build issue we are having currently. Out .config files default to haveing a defaultframework attribute of net-1.0. However on a 1.1 only platform we need to take a copy and change that attribute to net-1.1 or whatever the current framework is. I was going to write a custom task to do it but <xmlpoke> looks like a better - more generalised way of doing it.
Ian
. The next three tasks which I plan on producing might be of more general use:
<xmlpeek filename="<path to xml file>" path="<xpath expression to find element or attribute>" property="<property to populate with value>" /> <xmlpoke filename="<path to xml file>" path="<xpath expression to find element or attribute>" value="<property to get the new value from>" /> <incrementversion property="<property holding a valid version number string>" part="build" />
The idea here is that with these three tasks you can do things like maintain a build version file in a project configuration file. I learned yesterday that Visual Build actually keeps a build number in the .bld file, and I was contemplating using the above tasks to emulate that by using the peek and poke commands to set some global project properties. I would be interested in peoples thoughts on this. These new tasks combined with the stock standard NAnt tasks pretty much take care of the whole build versioning process.
I'll happily donate what I can (if anyone is interested). But it will have to wait until I can rewrite what I have to comply with the NAnt project coding standards and unit test requirements.
----------------------------------------
- Mitch Denny
- [EMAIL PROTECTED]
- http://www.monash.net
- +61 (414) 610141
-
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
