On 9/6/05, Andy Johnstone <[EMAIL PROTECTED]> wrote: > HI all, > > I have a folder structure which stores releases in a known location. > > The pattern is: > c:\releases\<project.name>\ - This level will always contain the latest > version of the DLL > c:\releases\<project.name>\<a.b.c.d>\ - This level stores archived versions > of the DLL, where a.b.c.d is a version number. > > Using this pattern, the <solution> task finds the appropriate dependancy DLL > to build against: > > <include name="c:/releases/**"/> > <exclude name="c:/releases/**/????.?*.?*.?*/*.dll"/>
If your DLL is always at the top level of your project, you can use a single non-recursive pattern: <include name="C:/releases/*/*.dll"/> This won't include any of your archived DLLs because it doesn't recurse into sub-folders... the lack of recursion should also improve the fileset scanning performance, which can be a bonus on large directory trees! In general, it is often easier to be more specific when specifying include patterns, rather than including everything and then relying on exclude patterns to trim the list, unless you have a small number of simple file patterns to exclude. Hope that helps, -- Troy ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
