RE: [Nant-users] Problem using NAnt 0.8.4

2004-10-25 Thread Gert Driesen
Rajeev, You can try using a recent nightly build of NAnt (http://nant.sourceforge.net/nightly/builds), as we now by default target the latest .NET runtime installed. About your build failure : we can't tell what might be causing this if you don't provide more information. Can you create a debug

[Nant-users] Problem using NAnt 0.8.4

2004-10-25 Thread rajeev vashist
Hi,     I want to use the NAnt with the web application in .net but i don't know the exact way even then i am using by reading the help.   but there is a problem in using this that i have .net 1.1 version on my system but in the NAnt by default 1.0.   at first i've downloaded this on my d

[Nant-users] foreach: Too many items on line

2004-10-25 Thread Felice Vittoria
Hello all, I'm having a little issue.I exported my scheduled tasks into a csv file using the command: schtasks /query /fo csv /s dcweb1 /v > test.tasks.csv When I run the following script:

RE: [Nant-users] Problem with passing Environment Variables to the Exec task.

2004-10-25 Thread Shawn Haigh
Hey Fritz, thanks for the reply!   I am not an expert user either, even if I knew how to convert the make to Nant, I am using a third party SDK and we don’t want to modify anything, or at least convert every time they release a new SDK. So I am still left with the same dilemma.   Regard

[Nant-users] Problem with passing Environment Variables to the Exec task.

2004-10-25 Thread Shawn Haigh
Greetings all   I am having a problem with passing environment variables to an exec task. Basically I am trying to convert what we do using regular .bat files to a NAnt equivalent.   I am using a nightly build of NAnt v0.85-20041006 Platform: Win2000 server sp4    Here is an example

Re: [Nant-users] "Property name 'sys.env.;PATH' is invalid." error with sysinfo.

2004-10-25 Thread John Debay
on 10/22/2004 7:30 PM Merrill Cornish wrote: John, I don't know if this is a typo, but 'sys.env.;PATH' has an illegal character in it: the semi-colon. Also, from the DOS prompt, issue a "set" to see _exactly_ what capitalization of "PATH" is on your machine. For example, on my Windows XP Pro,