Ian,
First, thanks for humoring me on this. I'm not sure whether I should
apologize for going on about this. I'm new here. My original impetus
for joining the list was that taskdef is exactly what I wanted and I
couldn't find it w/o hassle.
> What I'm looking at adding is an additional setting in the
> config file
> which is a list of folders to look for task assemblies in.
So I'd have to preserve "my" part of the config file when I update Nant,
instead of preserving my *Tasks.dll. I'm not sure there's a gain.
> Is copying a couple of files really jumping thru hoops ? The
> config file
> options I mentioned above would eliminate this step anyway.
Same problem, different representation. And it's not just "a couple of
files". It could be a whole bunch of dll's from different sources, in
different versions.
Also, is it me or is there a problem w/ the copying of the new build of
a customTasks.dll into ${Nant.Location} while nant is running, holding
the target dll?
Also also, my point is: why subtract from Nant.Core? Flexibility is
good. You say
> Personally I find the taskdef mechanism a bit clunky for NAnt.
To each her own. taskdef suits my entreprise's strategies better and I
don't understand the top-down decision of subtracting it from the core.
We've probably said enough at this point. Again, thanks for your
persistence.
/Jean
P.s., is it me or does this list hiccup? (I get many same messages).
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
