Carlton,
NAnt 0.84 does not support NUnit 2.2. NAnt 0.85 wil support NUnit 2.2
though. You can already download a (stable) nightly build here :
http://nant.sourceforge.net/nightly/builds.
Hope this helps,
Gert
- Original Message -
From: "Carlton Nettleton" <[EMAIL PROTECTED]>
To: <[EMAI
Jon,
You need to pass the property name as a string like:
${property::exists('version')}
if not the 'value' of the property will be passed to the exists function and of course
this will fail if the property doesn't exist.
Ian
Pietig, Jon wrote:
When I use the property::exists(property) function on
I am using nant 0.84 and I was wondering if the task supports
NUnit2.2? I can get my code to compile, but I get this message about my
unit tests.
[nunit2]
This is very odd considering I do have unit tests and they run fine in
the GUI portion of Nunit 2.2. Do the later versions of Nant
Title: Problem using property::exists(property) function
When I use the property::exists(property) function on a property that doesn't exist in the build file or wasn't passed in on the commandline I get the following error:
Property evaluation failed.
John,
I'm not sure how your script it setup but this *is* possible.
For one, I would change the line: ${projectdir}/debug/bin
to: ${projectdir}/${build.type}/bin
That would take care for debug/release directories.
I would also incorporate the same changes in your csc targets.
>From readin
Hi,
I want to create a NAnt build script that can easily handle either debug or
release builds, or both. In other words, from the command line, I want to be
able to do any of:
nant debug // creates debug build
nant release// creates release build
nant all/
Hello,
I have recent builds of nant and nantcontrib.
NAnt.Core.dll 0.85.1706.0
NAnt.Contrib.Tasks.dll 0.85.1692.0
Does anyone know why I would be getting the below error?
C:\data\projects\IDS 4.0\Server 4\Source\default.build(109,14):
Specify either an "assembly" attribute
>From: "Patrik Fors" <[EMAIL PROTECTED]>
>Sent: Thursday, September 02, 2004 9:49 AM
>This is kinda off topic but nant users are probably the most likely to
>know of a solution..
Try this: Put the C# code into a regular C# project, but disable that
project from building in the Visual Studio Conf
Can anyone explain this to me? Is it a bug or a feature? This code:
inside foreach: my.version = ${my.version}
after foreach: my.version = ${my.version}
Produces this output:
[echo] inside foreach: my.version = 1.0.7.4254
BUILD FAILED
c:\Integrator\scripts\integrator.nant.bui
I'm a little confused. I thought function (and custom function) support
was added to NAnt 0.85? And if that's true, then why not use
string::replace()? At least for this simple example of changing '.' to
'_' string::replace() would work perfectly well.
--
Edwin G. Castro
Firing Systems Engineer
[
Shawn,
Here is my custom action and an example build file. Is this what your
looking for? pSearch is a regular expression.
-
Hi!
This is kinda off topic but nant users are probably the most likely to
know of a solution..
In a project im working with we're using Nant to build a c# project
since we experience build problems when using the studio. It has
something to with targeting both pocketpc and windows platform. We'r
Shawn,
If you want to leap using nant 0.85 then you can use the string::replace
function. So, it would be something like:
${string::replace(build.number,'.','_')}
Otherwise (for Nant 0.84) , you'll have to do something what's posted in
an earlier thread ( http://www.mail-archive.com/na
I was kind of confused but I think the addition of the example to the
nightly build docs would have solved it. Unfortunately for me I was looking
at the docs that came with my build :-). The fourth example clarifies this
use very nicely. Thanks!
Kevin
-Original Message-
From: [EMAIL PR
14 matches
Mail list logo
