[NAnt-users] Best Practices for Multi-File Build Targets

I split my build files up based on common functionality (compile.build, test.build, database.build, helpers.build, analysis.build, etc) and include them all at the top of my main.build file. This causes me some problems because loading all the build files (and related task assemblies) is rather slo

[NAnt-users] Best Practices For the Co-existence of NAnt and GNU Make

Hello All, I am working on a project that uses a combination of .NET Technology and Native Llibraries. Some of the Native Libraries have wonderful Makefiles that I do NOT want to port to NAnt. I've looked high and low and have not been unable to find any elegant examples of the marriage between

Re: [NAnt-users] Best practices for NANT

ant-users@lists.sourceforge.net Subject: [NAnt-users] Best practices for NANT Do we have best practices documents of NANT on windows which one should follow while framing their build process ? For example, there should be one default.build file for every module or solution, there should be

[NAnt-users] Best practices for NANT

Do we have best practices documents of NANT on windows which one should follow while framing their build process ? For example, there should be one default.build file for every module or solution, there should be one target, rebuild, which will call all other targets etc.. Thanks! Rajiv

Re: [Nant-users] Best practices for subprojects when using custom tasks.

Foster, Richard - PAL wrote: Hi there, Sorry in advance if this question is somewhat esoteric! We have a project made up of several components. Until now, we have created build files for each of the components, then called those build files (using the NANT task) from a central application build f

[Nant-users] Best practices for subprojects when using custom tasks.

Title: Best practices for subprojects when using custom tasks. Hi there, Sorry in advance if this question is somewhat esoteric! We have a project made up of several components. Until now, we have created build files for each of the components, then called those build files (using the NAN

RE: [Nant-users] Best practices for portable NAnt Environments... [1 more try]

egistry yourself, to allow NAnt to automatically discover that you have installed the SDK.   Hope this helps,   Gert From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron ElderSent: woensdag 1 december 2004 6:14To: [EMAIL PROTECTED]Subject: [Nant-users] Best practic

[Nant-users] Best practices for portable NAnt Environments... [1 more try]

Sending again since there was no response.  Thanks!       Here is what I would like,   I would like to be able to check into my source control system NAnt as well as a copy of the .NET compiler (v1.1 & v1.0).  When developers sync to the project, they will always be syncing to a s

[Nant-users] Best practices for portable NAnt Environments...

Here is what I would like,   I would like to be able to check into my source control system NAnt as well as a copy of the .NET compiler (v1.1 & v1.0).  When developers sync to the project, they will always be syncing to a single controlled build environment.  The trick is…   How do I te

[Nant-users] Best practices

I am in the process of converting our existing build enviroment over to NAnt and wanted to get the lists thoughts on some best practices. Our build currently consists of a makefile that shells out to devenv compiling approximately 75 solutions files, that generate over 150 assemblies. There are a