I see the same problem in the latest download of mono 2.4 on mac. Adding
/Library/Frameworks/Mono.framework/Versions/2.4/bin to PATH seems to resolve
the issue for me
Raj
On Fri, Apr 24, 2009 at 7:47 AM, Gert Driesen wrote:
> Hi Ron,
>
> From the error it's clear that NAnt cannot start pkg-conf
I will try to put together a proposal in the next couple of days.
The following is subject to memory fade as I looked at it a few years
ago and started to explore a solution.
I had considered extending the property system to include a form of
scoping. Limiting visibility of a parameter or o
Seems like I should just create a task in the script code and then call the
task. Would be about the same amount of code, right? I just have to put the
after the script task.
I never created a task inline. But, since there is no way to sort a fileset I
am finding I have to do some c# code here
Hi Bob,
This is only done when logging from a task.
You could do something like this (although I agree it's a hack):
Would it be better to create a function or a task that you can pass stuff to,
rather than having to worry about property scoping?
BOb
From: Gert Driesen [mailto:gert.drie...@telenet.be]
Sent: Wednesday, May 13, 2009 3:04 PM
To: 'Bjerstedt, Tony [Audatex - Americ
Ok,
I am trying to log from code in a script task. I use code such as this:
project.Log(Level.Info, "I am in the script function.");
But the console log looks like this:
[script] Scanning assembly "tommx7ja" for extensions.
I am in the script function.
What is it not formatted t
Hi Ken, Tony,
This is definitely something that I've considered as well.
Can one of you work out a proposal that can be discussed on the list?
Gert
From: Bjerstedt, Tony [Audatex - Americas]
[mailto:tony.bjerst...@audatex.com]
Sent: woensdag 13 mei 2009 20:01
To: Parrish, Ken; nant-us
I have wondered the same thing. If this were added, I would suggest an
approach similar to XSLT.
An XSLT like approach would look something like:
...
and
Has there ever been any consideration to creating a mechanism for executing the
task with a set of private, local parameters (properties) which are only
available inside the called task?
I'm not sure exactly how the syntax would work, but the idea would be to pass,
as an argument to the task,
