> would folks consider adding an
> additional enumeration called "ChildFolders" or
> "ChildDirectories" to the type list?
Rather than add extra attributes and work into foreach for variant
behaviour, I would suggest using functions to vary the standard
behaviour.
eg: the path::get-file-name fun
After a brief flirtation with MSBuild, I've been spending some quality time again
recently with NAnt. I'm creating a rather complex build script that I'm using to
generate courseware. There's a couple of things that have been bugging me about NAnt,
and which I've fixed in my private build, but I
Hi all,
is no longer valid in recent cvs version. This is
becouse of
public
string Delimiter {
get
{ return _delim; }
set
{ _delim =
StringUtils.ConvertEmptyToNull(value);}
}
and
ConvertEmptyToNull does trimming into its value. So
delimiter is null and
throw new BuildExc
ogesh Shetty [mailto:[EMAIL PROTECTED]
Sent: donderdag 21 augustus 2003 13:23
To: [EMAIL PROTECTED]
Subject: [nant-dev] foreach
I am not able to figure out what is the problem in below fragment.. it
I am not able to figure out what is the problem in below fragment.. it use
to work before
This should give me the list of all filename starting with m.. spend an hour
in resolving this issue but no luck...
Regards
Yogesh S
For #1, the "in" attribute probably shouldn't be used when you're using
a fileset. If you want to specify a directory to start the search from,
use the "basedir" attribute on the element.
For #2, I had to do something similar and the only way I know of to do
it (without
I am stucked up with 2 problems
Problem 1 :
The above foreach tags must retrieve all those files having medco as prefix
but this retrieves all files. but when i remove the in="${OutputFolder}"
then it works as expected. seems to be a bug