Re: [NAnt-users] nant-0.91-alpha1 Build & Windows 7/2008

The 0.91-nightly-2010-05-12 build didn't work for me. However if I force the runtime to .NET 4 within the NAnt.exe.config file, this seems to clear the problem: .... Darren Syzling mailto:darren.syzl...@optial.com www.optial.com<http://www.op

RE: [Nant-users] support for property files ?

Jean, Thanks for the comments. In the end reviewing solutions and considering how easy it is to create NAnt custom tasks I decided to create my own local PropertyFile task. Overall it improved readability within the build file and the implementation was quite trivial. Thanks Darren Syzling

RE: [Nant-users] support for property files ?

ation. I'd also like to batch build each customer in turn, which relies on being able to set the properties within a target and repeat for each client. Unless I'm wrong in this scenario the task wouldn't work, although may be useful? Darren Syzling mailto:[EMAIL PROTECTED] h

[Nant-users] FW: nunit2 and config file probe path

ttribute shouldn't nunit2 just default to assembly-filename.config if the file is present? Regards Darren -----Original Message- From: Darren Syzling [mailto:[EMAIL PROTECTED] Sent: 29 May 2003 13:11 To: '[EMAIL PROTECTED]' Subject: nunit2 and config file probe path I

[Nant-users] nunit2 and config file probe path

ast night's snapshot (0.8.3 ?) and this exhibits the same behaviour. Darren Syzling mailto:[EMAIL PROTECTED] --- This message may contain information which is confidential or privileged. If you are not the intended recipient, please advise the send

RE: [Nant-users] recursive compile

You can get the same affect using a file spec of '**/*.cs', e.g: Regards Darren -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Attale, Pramith BGI UK Sent: 03 March 2003 10:43 To: '[EMAIL PROTECTED]' Subject: [Nant-users] recursive compile Is it poss

RE: [Nant-users] fileset parameterisation

of Ant and I'm struggling to share build rules across multiple components without it. Darren -Original Message- From: Scott Hernandez [mailto:[EMAIL PROTECTED]] Sent: 06 January 2003 22:15 To: Darren Syzling; [EMAIL PROTECTED] Subject: Re: [Nant-users] fileset parameterisation

[Nant-users] fileset parameterisation

I'd like to be able to centralise my build rules wherever possible. Is it possible to parameterise filesets, for example the 'sources' and 'references' elements of the csc task. The docs suggest that all Filesets are comma separated lists of file specifications. My attempts to build a comma se

RE: [Nant-users] nant task and basedir property

chive). Removing the basedir property fixed the include task problem and set the current directory correctly for the called build file. Darren -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Darren Syzling Sent: 23 December 2002 23:19 To: [EMAIL PROT

[Nant-users] nant task and basedir property

I'm not sure I understand the relationship between the nant task and the basedir property of the called build file. If a top level build file calls a lower level build file using the nant task and the called build file basedir is '.' any operations will be performed in the current directory where

RE: [Nant-users] Including central build rules

file. Darren -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Darren Syzling Sent: 23 December 2002 22:05 To: [EMAIL PROTECTED] Subject: [Nant-users] Including central build rules I'm trying to centralise some of my build rules using entity declar

[Nant-users] Including central build rules

I'm trying to centralise some of my build rules using entity declarations and including within a Nant build file. Something like: ]> and then including the entity declaration within the project section: &common-build-rules; I receive: INTERNAL ERROR System.NullReferenceException: Objec