What may be cleaner than directly writing the child build scripts using
the task is to use XML/XSLT to template your build
scripts...
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 simp
Selke, Anthony wrote:
Ouch. I really hoped to avoid building the file from scratch (hence the
tag). What about the 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
> Does CI mean "check in " or "continuous integration"?
Sorry ... continuous integration, though I am doing my testing running
Nant directly from the command line.
> NAnt only deals with the if/unless/ifnot control
> facilities at the task level.
Ouch. I really hoped to avoid building the file
Selke, Anthony wrote:
I am putting together a CI build process and trying to do so in such a
way that it is as simple as possible to add new projects.
Does CI mean "check in " or "continuous integration" (not that it's
really relevant to the question)?
All of our projects are done in Visual Stud
