On Wed, 23 Feb 2005 10:21:59 -0800, Jeff Rodenburg <[EMAIL PROTECTED]> wrote: > My questions: > - Do I require the individual .csproj files to be current for a NAnt > build script? Do I have other options to use besides those files? The csc task can build source files based on patterns, lists, whatever. So something like
<csc> <sources> <include name="src/*.cs"> </sources> </csc> is totally legal... > - Can I avoid the use of .csproj files altogether for the build > routine? If so, can I construct the build script in such a way that I'm > not required to provide specific file/folder names? See above for including sources in assembly building. The model I use is: each project has a build file. the build file includes sources based on patterns. the build file is created from a template domain-specific knowledge within a project build file is limited to; project name, project references. project build scripts can be executed alone, or are controlled by a main build script. > - Is there a better way to go about this? I'm sure there are other solutions also. A side-effect to note of this model is that sources removed from the repository may potentially still exist locally. The build script lacking a source list will still include those sources in any builds until they are removed. I hope this is helpful -josh ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
