Gary,
>>>why not just right a shell script (bash, not Windows shell) wrapper for calling
>>>NAnt?
For one reason, we are all running on Windows, so bash isn't automatically available.
Yes, I know we could install a Windows version of bash, but I don't want to get into
the position of having t
>From: "Merrill Cornish" <[EMAIL PROTECTED]>
>Sent: Wednesday, August 11, 2004 11:36 AM
> I'm a bit anal in that I spend a good bit of time on the user
> interface to my scripts, even if that interface is just a lowly
> command line. I do things like validating parameter values,
In the intere
Gert,
>>> What exactly do you need it for ?
I've wished on several occassions for the ability to treat the target name(s) at the
end of the nant command line as if they were command line parameters that could be
detected in the script.
I'm a bit anal in that I spend a good bit of time on the u
:04 PM
Subject: [Nant-users] get name of current target
> Hello,
>
> I use a nightly build (July 04) of nant-0.8.5.
>
> My build-script has following structure:
>
>
>
>
>
>...
>
>...
>
>
>
>
>...
>
>
&
Hello,
I use a nightly build (July 04) of nant-0.8.5.
My build-script has following structure:
...
...
...
Within the "gobal section" I want to retrieve
the name of the target currently to be build.
The function "target::get-current-target"
grumbles "No targ
