Heya Prasad,
You can use the move task:
Documentation for move can be found here:
http://nant.sourceforge.net/release/latest/help/tasks/move.html
Cheers,
Matt
On 9/19/05, nbl prasad <[EMAIL PROTECTED]> wro
Heya Merrill,
> If you parse tasks, then you would also (I think) have to parse
> properties
> since the include pathname could be defined by property expansion. However,
> properties can be conditionalized by tasks, so they have to be parsed,
> and
> properties get defaults by command lin
Heya Ian,
> >Would anyone be interested in a patch for that behaviour? Or is it
> >undesirable (as it seemed to be for Gary at least)?
> >
> >
> Definately.
I take it that definitely was directed at the "interested in a patch". ;)
> I vaguely started looking at it a while ago but didn't get
>
Thanks for all your help folks. A custom help task ought to do the
job. Still seems to me that -projecthelp should parse any include
tags but hey, I can live with that limitation! :)
Would anyone be interested in a patch for that behaviour? Or is it
undesirable (as it seemed to be for Gary at
Heya Guys,
I'm trying to shift some common targets into one NAnt script and use
those operations from multiple NAnt scripts.
Something like this:
And this:
Which works fine. :) What I'd like to
The need to write to the registry has been logged here:
http://tinyurl.com/ch5qm
There's also a simple example implementation posted there that you
could use. I've got similar needs in the near future so I may polish
that implementation up a bit - if I do so I'll update that feature
request so
Alternatively, if you have Visual Studio installed you can use an exec
task to call devenv with the 'clean' option before building.
Something like this:
It would be nice to have a 'clean' attribute for the solution task though...
Cheers,
Matt
On 8/10/05, Tim Posey <[EMAIL PROTECTED]> wrote:
