>I'm not sure that multiple filesets in a single copy task is much better
>than multiple copy tasks.
Here's why I think its more than a slight improvement:
The core problem is duplication. I finished the refactoring that lead to
my OP and here's where it stands:
The goal is to copy assemblies
Interesting. If you look at CompilerBase.cs you can see that it allows
multiple resourceFilesets. This is allows you to use different prefixes
for different groups of files and so fileset merging wouldn't work there.
I'm not sure that multiple filesets in a single copy task is much better
than
ll not sure how about xml merge of
such filesets
Martin
- Original Message -
From: "William E Caputo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 13, 2004 1:48 PM
Subject: Re: [nant-dev] FileSetCollection and the copy task questions
> Mart
Martin Aliger:
>We are currently extending fileset to enable add something to existing
>fileset.
Yes, that would work for the example I sent (I thought about your recent
posts after I sent my email). After sending, I realized that the
refactoring I was doing also needed to do something like this
- Original Message -
From: "William E Caputo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 13, 2004 5:00 AM
Subject: [nant-dev] FileSetCollection and the copy task questions
> Hi All,
>
> I am making sure I am not missing anything. I wo
Hi All,
I am making sure I am not missing anything. I would like to use the copy
task with multiple filesets like so:
The advantage of being able to do this is to be better able to factor out
duplication (without having to duplicate otherwise identical copy tasks,
that could ev
