http://nant.sourceforge.net/release/latest/help/tasks/style.html
It would probably yield a more maintainable script in the long run, since XSLT should be much simpler to edit - if done using the common single-template many-foreach style, the XSLT almost looks the same as the XML it will produce. It's just at the downside of yet another language in the mix. Still, in this kind of case I think it's worth it.
-T
On 4/20/05, Ashley Moran <[EMAIL PROTECTED]> wrote:
Selke, Anthony wrote:
> Ouch. I really hoped to avoid building the file from scratch (hence the
> <solution> tag). What about the <foreach> node? I have the following:
Actually I've just done a similar thing- dynamically generating a nant
script (although mine was for customised remote application installs.
What you do is something like this:
<echo file="solution.build" append="true">
<solution ... >
<webmap>
</echo>
<foreach item="Line" in="webmap.config" delim="|" property="url,path">
<echo file="solution.build " append="true">
<map url="" path="${ccnet.working.directory}\${path}"/>
</echo>
</foreach>
<echo file="solution.build" append="true">
</webmap>
</solution>
</echo>
<nant buildfile="solution.build"/>
Be warned that I just wrote this straight in Thunderbird so I have no
idea if it will work (but the idea is there)
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
Nant-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nant-users
--
Troy
