RE: [NAnt-users] Incorporating NAntContrib into NAnt

[Foster, Richard - PAL]

Title: Incorporating NAntContrib into NAnt

That's one of the reasons I like keeping NAnt & NantContrib under source code control too. That way when someone pulls the latest version of the build scripts, they also get a version of the tools that understand it.   Just my personal preference....   Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Cole Sent: Wednesday, March 15, 2006 16:14 To: 'Bill Martin'; 'Crawford, Christina'; nant-users@lists.sourceforge.net Subject: RE: [NAnt-users] Incorporating NAntContrib into NAnt Bill,   The disadvantages of the "recommended" way are:   * If you have lots of build files (we have hundreds in multiple branches in cvs) you would have to change each file. * If you install on several machines (about 20 here) then you need to keep track of what versions of NAnt and NAntContrib your running.  It's a lot easier if you install NAnt and NAntContrib as a set. * If someone puts NAntContrib on a different path (some C: drives are FAT32 and they install on a NTFS on D: ) then that person can't run the same script as the person who installed in C:/NAntContrib without modifying them.     The "easy" way as the advantage of forgoing all of those problems and you just need to put the nant install dir in your environment path.  We build lots of NAnt/NAntContrib installs and we never build one without building the other.      My opinion has always been that building the NAnt MSI installer was the best way for windows users to install NAnt/NAntContrib, but I haven't been able to get the MSI built in months (our version is 1927 from May of last year).     But either way works.   John Cole   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Martin Sent: Wednesday, March 15, 2006 2:39 PM To: 'Crawford, Christina'; nant-users@lists.sourceforge.net Subject: RE: [NAnt-users] Incorporating NAntContrib into NAnt   Christina,   There are two ways to accomplish this.  The "easy" way is to copy the content of the NAntContrib bin folder into the NAnt bin folder, however this is not the recommended way.   The recommended way is to install NAntContrib to a separate location and use the <loadtasks> task to load the necessary assemblies.  This would be something like:   <loadtasks>             <fileset>                         <include name="c:/NAntContrib/bin/**/*.dll" />             </fileset> </loadtasks>   The advantage of doing it this way is that if you upgrade your version of NAnt, you don't need to remember what additional files you had in your NAnt bin folder to get all your scripts running.   HTH,   Bill   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Crawford, Christina Sent: 15 March 2006 20:09 To: nant-users@lists.sourceforge.net Subject: [NAnt-users] Incorporating NAntContrib into NAnt   What is the best way to incorporate the NAntContrib tasks and functions into the Current Nant product?  I want to be able to use NAntContrib functions and tasks In my Nant build file and don't see any references to the Nantcontrib dll's anywhere Within Nant. Christina Crawford