The Fine Manual says, "File Sets can appear inside tasks that support
this feature or at the project level, i.e., as children of project."
But I had trouble figuring out how to use the children of project
feature... to keep as much of the build script to cut-paste-and-pray as
possible. What I wanted to do was:
<csc output="${builddir}bin\${assemblyname}" target="library"
debug="${debug}">
<references basedir="${referencedir}" fileset="References" />
<sources basedir="${builddir}" fileset="Sources" />
<resources basedir="${builddir}" fileset="Resources" />
</csc>
And I'm happy to report that I can! But the ID attribute of the fileset
was the undocumented bit.
<fileset id="References">
<includes asis="true" name="System.dll"/>
...
<includes name="Xolutions.Data.Sql.dll"/>
</fileset>
However, the copy task no workie like the csc task. :( Kind of a kink
in the usefulness. I would've expected this to do the trick:
<copy todir="${integrationdir}\bin"
basedir="${referencedir}" fileset="References" />
I'm hoping I just overlooked it in my haste to lay waste... but it's
handy enough to be able to setup a named file set at the top of build
and re-use it through-out for various purposes (zip these, get these
from SCC, build these, copy these...), that I thought I'd wonder who out
loud who I should send some documentation additions to? (And maybe
whine a little bit that COPY and VSSGET doesn't support a filesets
attribute, yet. :)
<blantant_newbie_whining>
The NAnt website documentation could use some freshening... Has anybody
considering adding a column to the Task page (and attributes) that
indicates which version first supports the feature? Might reduce the
number of different sets of dox and certainly my confoundedness.
Since I hate whiners, how does one go about volunteering to splotch in
some new documentation patches? I'm also putting together a Textpad
syntax file and Visual Studio schema (to support tag autocompletion) if
anybody's interested.
While you're at it, would somebody please kill the nantcontrib project
at SF? The fact that it's out there and can be found is likely to cause
people like me to continue to hurt themselves... :) I wasted more time
trying to get cvs and nantcontrib to work than I did just commenting out
the mainline NAnt RC2 unit tests that don't work for some reason and
just using the RC2 version.
Slip-streaming all the contributions was the best idea! Thank you,
masked man.
</blantant_newbie_whining>
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
