Yeah -- I used to do that as well, until I ran into incompatibility issues with diff vers of NANT on multiple diff OSS projects all on my same PC that took me *forever* to troubleshoot my way through. Now no more 'ubiquitous' NANT in my path :)
YMMV in all cases, of course so stick with what works~! Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Fri, Sep 24, 2010 at 8:40 AM, Valeriu Caraulean <[email protected]>wrote: > It should work this way too, haven't checked... > For me it's just more comfortable having it in the path and don't bother > taping paths. > > Cheers. > > > On Fri, Sep 24, 2010 at 2:23 PM, Stephen Bohlen <[email protected]> wrote: > >> I don't believe that's actually true. If you invoke nant via an explicit >> path (e.g. C:\myStuff\Nant.exe) but your currect active dir is the same as >> contains the build file(s) it should still work without having NAnt on your >> path. >> >> This is how I run the NH NAnt scripts all the time. Does this not work for >> you --? >> >> >> -Steve B. >> ------------------------------ >> *From: * Valeriu Caraulean <[email protected]> >> *Sender: * [email protected] >> *Date: *Fri, 24 Sep 2010 11:19:38 +0200 >> *To: *<[email protected]> >> *ReplyTo: * [email protected] >> *Subject: *Re: [nhibernate-development] Missing AssemblyInfo file? >> >> Yes, you need NAnt to be installed and registered in your path. >> >> On Fri, Sep 24, 2010 at 11:04 AM, Graham Bunce >> <[email protected]>wrote: >> >>> Hi, >>> >>> I'd like to start contributing some patches for NH so got the latest >>> code from trunk through my SVN client. When I opened the source code >>> in VS2008 and tried to build I noticed the AssemblyInfo.cs files are >>> missing i.e. they are not in SVN. >>> >>> I can just go ahead and create dummy versions on my disk to get round >>> this, but should I not be building in this way - do I have to use the >>> NANT scripts? Do these create the AssemblyInfo files in your TeamCity >>> build process? >>> >>> Cheers >> >> >> >
