Reopened #s bug (was: RE: [nant-dev] #s break nant)

2002-06-05 Thread Nathan Sharfi
ILED D:\projects\C(21,14): Error creating file set. Could not find a part of the path "D:\projects\src". Try 'nant -help' for more information -Original Message- From: Gerry Shaw [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 01, 2002 6:58 AM To: 'Nathan Sharfi'

RE: [nant-dev] #s break nant

2002-05-25 Thread Nathan Sharfi
One other thing: I noticed that after doing all this testing, I found both 'Debug' and 'Release' directories in D:\projects. ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devco

[nant-dev] #s break nant

2002-05-25 Thread Nathan Sharfi
having #s in a path to a buildfile (or perhaps sets) seem to break nant. Consider this exchange I had: = D:\projects\CS#\Orbital>nant Buildfile: file:///D:/projects/CS#/Orbital/Orbital.build build: debug: BUILD FAILED D:\projects\CS(21,14):

[nant-dev] What does the task do?

2002-05-05 Thread Nathan Sharfi
The Vb6 task seems to be a copy of Tlbimp's. Shouldn't it be removed? ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]

[nant-dev] Documentation Fixes for a few classes

2002-05-04 Thread Nathan Sharfi
Patched against http://nant.sourceforge.net/snapshot/nant-snapshot-20020503.zip ClTask.cs.patch Description: Binary data AlTask.cs.patch Description: Binary data CscTask.cs.patch Description: Binary data

[nant-dev] 'nant userdoc' doesn't work here (Was: RE: some documentation related fixes)

2002-04-25 Thread Nathan Sharfi
Kaboom! perhaps I'll try again tomorrow. I downloaded the thing about five minutes earlier. Autopsy: D:\etc\nant-snapshot-20020425\nant>nant userdoc Buildfile: D:\etc\nant-snapshot-20020425\nant\NAnt.build [tstamp] Thursday, April 25, 2002 9:11:30 PM build: [mkdir] Creating directory D:\

[nant-dev] New Documentation beta up

2002-04-22 Thread Nathan Sharfi
I thought the existing nant documentation was lacking, and also wanted to increase my xsl-fu. Hence, I'm converting the existing documentation to XML and using XSL to get html files. as you can see, I don't use MS' msxsl command-line util; I use one that's available from http://www.fh-frankfurt.de