Tomas Restrepo wrote:
> What I'd like to have is a property (let's call it nant.location for now),
> the value of which would contain the complete path to the directoy nant is
> being loaded from. I know it doesn't sound like much, but it's really a two
> line change in Project.cs and would allow us to create more portable
> buildfiles that referenced dlls included with NAnt.
> For example, it would make it easier to build new assemblies containing
> additional NAnt tasks (such as the upcoming NAntContrib project), since you
> wouldn't need to know where nant.core.dll is located, so one could just put
> in the buildfile:
> <references>
> <includes name="${nant.location}\nant.core.dll"/>
> </references>
While I'm not disagreeing with the utility of this, I think you'll find that
as long as NAnt is on the path, you can do:
<references>
<includes name="nant.core.dll" frompath="true" />
</references>
and it will be properly referenced. I added this to NAnt a little while ago
to make building my unit tests easier. I don't think it's unreasonable to
expect that NAnt be on the PATH. :)
Brad
--
Read my web log at http://www.quality.nu/dotnetguy/
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
