At the risk of pulling a "hit 'em and split 'em" just before I go on vacation, I would like to propose something. I have been a Java developer for a few years now, and I am very used to the way ANT works. I was quite happy to see a .NET version available since I am now required to learn C#. That said, Java developers have to deal with an important concept called a "ClassPath" where all the JARs could be found. In .NET things are a bit better, but we still have to worry about where the assemblies are located in the system.
It is not uncommon to have to refer to other assemblies when they are not on your system PATH. The <csc> task has the proper element to reference assemblies, which is decent, but it doesn't translate to other tools like ndocs.
ANT provides a <path> type where we can predefine a path with a set of libraries so that things can be built much more easily, and we can include paths by reference as opposed to re-writing the same things over and over.
Consider this example:
<path name="build.path">
<fileset basedir="bin">
<includes name="*.dll"/>
</fileset>
</path><path name="test.path">
<path refid="build.path"/>
<location file="${nunit.dll}"/>
</path>
<target name="compile"> <csc> <assembly-path refid="build.path"/> <!-- ... --> </csc> </target>
It just makes things easier to manage. I can use the same path id for ndocs, csc, nunit, etc. etc. etc.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
