> Agreed- it's much clearer in that case. I think that > xmlpeek/xmlpoke/xmlforeach would be a powerful combination. Having an > implicit XML context available to all three would also be great! > > <xmlforeach id="configxml" ...>
what about to introduce new type (e.g. <xml id='...'>) and operations like xmlpeek/xmlpoke/xmlforeach/... could work with it? It will have same context etc. Like filesets now. There could even be tasks which outputs xml type as result of something and you could iterate through it later. Maybe even solution task could output an xml type with information what happens during build (projects/errors/warnings/...) Just an idea for the New Year :-) Martin ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
