Do you have rights to the source for the task (i.e., is it produced by your
organization)? Seems to me that if you just lost the source then it'd be
worthwhile to decompile it with Reflector or something rather than try to
get hokey workarounds.
My $0.02.
Sam
--
As Daniel pointed out earlier in this thread path::get-directory-name is
just a wrapper around Path.GetDirectoryName() so it would be entirely
inconsistent to change it's behavior. Most NAnt functions are wrappers
around .NET functions, they should do exactly what the .NET function does,
as is t
Looks like the problem is namespaces. Even though the original XML doesn't
use prefixes, it does have a default namespace declaration so to use xpath
on it you need to declare namespaces and use a prefix in your xpath. Docs
on xmlpeek talk about namespaces and have a namespaces example.
http:/
Not sure if there's anything built in but we use a custom property to track
warnings and report it in the e-mail. Works well for us.
HTH,
Sam
---
We're Hiring! Seeking a passionate developer to join our team building Flex
based products. Position
Our build confirmation e-mail is now over 1mb and is mostly output from Copy
and Delete tasks. Is there any way to make these tasks less verbose, as in
output only the number of files copied/deleted or something less than the
complete file name for every file affected?
Thanks,
Sam
---
We just added an unzip task to our build script and are having permissions
problems with the unzipped files. Our Build user has read/write/modify
rights to the folder containing the source zip files and we confirmed the
source zip files inherit the permissions properly. However, when we use
unzi
