[Nant-users] NUNIT2 Task Not Stopping After Failure

Title: NUNIT2 Task Not Stopping After Failure It appears that failures on NUNIT2 tasks are not being detected.  Failure on the CSC task seems to work properly (subsequent dependent targets do not execute), but a failure on the NUNIT2 task does not appear to stop processing of subsequent targe

[Nant-users] deployment manifest

Title: deployment manifest We have been using nant for our builds and deploys for a while and it works great. I am wondering how people are producing a manifest for packages deployed to a machine. We have 5-16 applications with their associated dlls deployed to any given server and it wou

[Nant-users] Why use Nant?

I have been using Nant for quite awhile now and am extremely happy with it. I would not use anything else but my organization is questioning why we should be using Nant and not just use Visual Studio to do our builds. I am having a hard time replying back to management in terms that will be underst

Re: [Nant-users] Forcing a target to fail from

> The question has already been answered, but I'm curious. Is this the > entire script? Everything you do here can be done within pure NAnt. > Personally, I prefer to avoid dropping into scripts, because one never > knows who will be maintaining the build file in the future. > > Gary I would gu

Re: [Nant-users] Load tasks acting weird

Malcolm, I don't have NAnt installed here so can't verify, but perhaps it is having a problem with the '..' in the path? Try using ${path::combine(nant::get-base-directory(), '..\..\nantcontrib-0.85-rc3\bin')}, this is the recommended (if more verbose) method for creating a path relative to anoth

Re: [Nant-users] Suppress framework warnings in NAnt log

Sandeep wrote: Hi, I get the following messages in the log when I run a NAnt script: NAnt 0.85 (Build 0.85.1932.0; rc3; 4/16/2005) Copyright (C) 2001-2005 Gerry Shaw http://nant.sourceforge.net Framework 'net-1.0' is invalid and has not been loaded : The 'System.dll' assembly does not ex

[Nant-users] Suppress framework warnings in NAnt log

Hi,   I get the following messages in the log when I run a NAnt script:   NAnt 0.85 (Build 0.85.1932.0; rc3; 4/16/2005) Copyright (C) 2001-2005 Gerry Shaw http://nant.sourceforge.net   Framework 'net-1.0' is invalid and has not been loaded : The 'System.dll' assembly does not exist

Re: [Nant-users] Stopping A Build

Taking a quick crack at it, try setting failonerror="true" the problem that I can see, is that failonerror defaults to true, are you setting it to false somewhere near the top of your script? I'm not sure if you even *can* set a global failonerror setting. Malcolm --- "Scott, Larry (TRIAD RE

[Nant-users] Stopping A Build

Title: Stopping A Build My NAnt scripts are not stopping when there is an error in some tasks.  It will stop if I have an error in a CSC task (building a C# application).  But when executing an 'nunit2'  task, and one of the test fails, I'd like to stop the process, but it continues executing

RE: [Nant-users] Load tasks acting weird - part 2

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Malcolm Anderson > Sent: woensdag 1 juni 2005 22:48 > To: Malcolm Anderson; nant-users@lists.sourceforge.net > Subject: Re: [Nant-users] Load tasks acting weird - part 2 > > ok, this is weird >

Re: [Nant-users] Load tasks acting weird - part 2

ok, this is weird gives me the same error, so I can't even hard code the path. I can however hard code the assembly That worked, so at least I can load the assemblies with out having to just dump all of nantcontrib/bin into the nant/bin as some posters have suggested. Thanks Malcolm ---

[Nant-users] Load tasks acting weird

I am trying to get my nant contrib task to load from a relative path. here's my tools directory C:\tools\ nantcontrib-0.85-rc3 nant-0.85-rc3 I have tried this, and this which should both work, but the error I'm getting for both is: notice

Re: [Nant-users] Forcing a target to fail from

Wilson, Glenn wrote: string targetEnv = project.Properties["target.env"]; switch(targetEnv.ToUpper()) { case "DEV": project.Properties["deployment.server"]="DevServer"; project.Properties["deployment.physical.path"

RE: [Nant-users] Satellite assemblies of referenced projects in solution task

> -Original Message- > From: Sjaak Janssen (Checkit) [mailto:[EMAIL PROTECTED] > Sent: woensdag 1 juni 2005 9:41 > To: Gert Driesen; nant-users@lists.sourceforge.net > Subject: RE: [Nant-users] Satellite assemblies of referenced > projects in solution task > > Gert, > > I've included a

RE: [Nant-users] Forcing a target to fail from

Thanks Thibault, that worked. Also, you may have spotted a mistake with the initial code sample I posted. It's only fair I put this right. I made a reference to a project property from inside the script using the "${property.name}" syntax. I should, of course, have referenced it through the "Pro

Re: [Nant-users] Forcing a target to fail from

Hi Glenn, try to throw a BuildException (NAnt.Core.BuildException). I'm doing this inside custom nant tasks to have the build fail, I suppose it should work just the same under a script block. kind regards Thibaut 2005/6/1, Wilson, Glenn <[EMAIL PROTECTED]>: > > > Hi, > > I have a target

[Nant-users] Forcing a target to fail from

Title: Forcing a target to fail from

RE: [Nant-users] Sql Script

Hi Paul,   My book Expert .Net Delivery with NAnt and CruiseControl.NET (http://www.amazon.com/exec/obidos/tg/detail/-/1590594851) covers this in some depth in chapter 8 Luckily you don't necessarily need to fork out for it as there is a sample chapter covering database stuff on the Apress s

Re: [Nant-users] Sql Script

Paul, This is indeed possible, but is likely to be dependent on the database server that you are using. I don't know of any NAnt tasks to do this for any database server, but if the database server provides a command-line interface for exporting a database into a sql script, then you could use th