um... It is possible to do this, pretty easily in fact(use
TaskContainer.AddPrivateXMLElementName(string)), but then it becomes a
little muddled in my mind about what is run, and what is part of the
<foreach>. You would be mixing stuff to do, with params and settings for the
task. If we allow elements inside the foreach then maybe the stuff that
should be done can be nested inside another element, like <do> or <execute>.
<foreach ...>
<setting1.../>
<setting2.../>
<other stuff related to foreach task...>
<do>
<!-- stuff to do -->
</do>
</>
instead of
<foreach setting1="" setting2="" ...>
<!-- stuff to do -->
</>
I'd lean towards using attributes if possible. It just seems cleaner in
terms of defining what the foreach will execute. But hey, I'm open to
opinions.
----- Original Message -----
From: "Matthew Mastracci" <[EMAIL PROTECTED]>
> Yeah- it would a bit more re-engineering, but I think that you are
> correct. Perhaps the same structure should be applied to the delim
> property as well.
>
> On Fri, 2003-02-28 at 02:34, Simon Steele wrote:
> > Wouldn't multiple sub-elements be the more XML thing to do?
> >
> > <foreach item="Line" in="C:\foo.txt" delim=",">
> > <property name="x" />
> > <property name="y" />
> > </foreach>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
