[nant-dev] Internal Error building NAntContrib

2002-12-11 Thread Greiner, Andrew
INTERNAL ERROR
System.MethodAccessException:
SourceForge.NAnt.TaskFactory.AddTasks(System.Reflection.Assembly)
   at NAnt.Contrib.Tasks.TaskDefTask.ExecuteTask()
   at SourceForge.NAnt.Task.Execute()
   at SourceForge.NAnt.Target.Execute()
   at SourceForge.NAnt.Target.Execute()
   at SourceForge.NAnt.Project.Execute(String targetName)
   at SourceForge.NAnt.Tasks.CallTask.ExecuteTask()
   at SourceForge.NAnt.Task.Execute()
   at SourceForge.NAnt.Target.Execute()
   at SourceForge.NAnt.Project.Execute(String targetName)
   at SourceForge.NAnt.Project.Execute()
   at SourceForge.NAnt.Project.Run()




---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



[nant-dev] How to get a copy working with NAntContrib

2002-12-11 Thread Greiner, Andrew
It seems that there is a little sync problem you guys have not resolved with
all these moving pieces.

How can I get a version of NAnt that will build the Slingshot project?

Right now I get error messages suggesting missing tasks.

Thanks

Andrew


---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



RE: [nant-dev] Command line parsing bug

2002-12-11 Thread Cort Schaefer
FYI: that is the default in Windows XP (and is the default behavior in a
Cygwin bash shell).

Cort

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Dag
Christensen
Sent: Wednesday, December 11, 2002 10:30 AM
To: [EMAIL PROTECTED]
Subject: RE: [nant-dev] Command line parsing bug

First the obvious to stay on topic, just so that I can include a neat
little hint :-)

Either there should be a try-catch around the Path.GetFullPath method,
or
(better) use Directory.GetFiles and loop through the files found to
allow
wildcards.

So the tip: if you want to avoid typing full directory and file names in
NT or later, modify the following registry keys:

HTLM\Software\Microsoft\Command Processor
CompletionChar=9
PathCompletionChar=9

Both are DWORDS. Start cmd.exe and you can use TAB to complete file
names
and loop through the matches found.

Dag

-Original Message-
From: Brian Davis [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 5:47 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] Command line parsing bug


New user to nant - not at the stage of trying to fix bugs myself yet, so
for
now I'll just report it as instructed :)

-

Probably worth catching errors like the one pasted below...
(I was attempting to avoid typing the full name of the build file)


D:\Temp>nant -buildfile:mybuildfile*
INTERNAL ERROR
System.ArgumentException: Illegal characters in path.
   at System.Security.Permissions.FileIOPermission.HasIllegalCha
   at System.Security.Permissions.FileIOPermission.AddPathList(F
h)
   at System.Security.Permissions.FileIOPermission..ctor(FileIOP
   at System.IO.Path.GetFullPath(String path)
   at SourceForge.NAnt.Location.Init(String fileName, Int32 line
   at SourceForge.NAnt.Location..ctor(String fileName)
   at SourceForge.NAnt.Project.LoadBuildFile(String source)
   at SourceForge.NAnt.Project..ctor(String source)
   at SourceForge.NAnt.NAnt.Main(String[] args)

Please send bug report to [EMAIL PROTECTED]





_
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
###

This message has been scanned by F-Secure Anti-Virus for Microsoft
Exchange.
For more information, connect to http://www.F-Secure.com/



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



RE: [nant-dev] Command line parsing bug

2002-12-11 Thread Dag Christensen
First the obvious to stay on topic, just so that I can include a neat
little hint :-)

Either there should be a try-catch around the Path.GetFullPath method, or
(better) use Directory.GetFiles and loop through the files found to allow
wildcards.

So the tip: if you want to avoid typing full directory and file names in
NT or later, modify the following registry keys:

HTLM\Software\Microsoft\Command Processor
CompletionChar=9
PathCompletionChar=9

Both are DWORDS. Start cmd.exe and you can use TAB to complete file names
and loop through the matches found.

Dag

-Original Message-
From: Brian Davis [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 5:47 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] Command line parsing bug


New user to nant - not at the stage of trying to fix bugs myself yet, so
for
now I'll just report it as instructed :)

-

Probably worth catching errors like the one pasted below...
(I was attempting to avoid typing the full name of the build file)


D:\Temp>nant -buildfile:mybuildfile*
INTERNAL ERROR
System.ArgumentException: Illegal characters in path.
   at System.Security.Permissions.FileIOPermission.HasIllegalCha
   at System.Security.Permissions.FileIOPermission.AddPathList(F
h)
   at System.Security.Permissions.FileIOPermission..ctor(FileIOP
   at System.IO.Path.GetFullPath(String path)
   at SourceForge.NAnt.Location.Init(String fileName, Int32 line
   at SourceForge.NAnt.Location..ctor(String fileName)
   at SourceForge.NAnt.Project.LoadBuildFile(String source)
   at SourceForge.NAnt.Project..ctor(String source)
   at SourceForge.NAnt.NAnt.Main(String[] args)

Please send bug report to [EMAIL PROTECTED]





_
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
###

This message has been scanned by F-Secure Anti-Virus for Microsoft
Exchange.
For more information, connect to http://www.F-Secure.com/



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



RE: [nant-dev] Command line parsing bug

2002-12-11 Thread Colin Young
I have a class I wrote that does some command line processing (the idea
was to make it easier to define switches and expand file names for
command line programs). It probably isn't the most elegant or powerful
bit of code in the world, but if whoever might look at this problem is
interested, I'd be happy to provide the code (either on this list or
directly to your email).

Colin

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Brian
Davis
Sent: Wednesday, December 11, 2002 11:47 AM
To: [EMAIL PROTECTED]
Subject: [nant-dev] Command line parsing bug


New user to nant - not at the stage of trying to fix bugs myself yet, so
for 
now I'll just report it as instructed :)

-

Probably worth catching errors like the one pasted below...
(I was attempting to avoid typing the full name of the build file)


D:\Temp>nant -buildfile:mybuildfile*
INTERNAL ERROR
System.ArgumentException: Illegal characters in path.
   at System.Security.Permissions.FileIOPermission.HasIllegalCha
   at System.Security.Permissions.FileIOPermission.AddPathList(F
h)
   at System.Security.Permissions.FileIOPermission..ctor(FileIOP
   at System.IO.Path.GetFullPath(String path)
   at SourceForge.NAnt.Location.Init(String fileName, Int32 line
   at SourceForge.NAnt.Location..ctor(String fileName)
   at SourceForge.NAnt.Project.LoadBuildFile(String source)
   at SourceForge.NAnt.Project..ctor(String source)
   at SourceForge.NAnt.NAnt.Main(String[] args)

Please send bug report to [EMAIL PROTECTED]





_
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers



[nant-dev] Command line parsing bug

2002-12-11 Thread Brian Davis
New user to nant - not at the stage of trying to fix bugs myself yet, so for 
now I'll just report it as instructed :)

-

Probably worth catching errors like the one pasted below...
(I was attempting to avoid typing the full name of the build file)


D:\Temp>nant -buildfile:mybuildfile*
INTERNAL ERROR
System.ArgumentException: Illegal characters in path.
  at System.Security.Permissions.FileIOPermission.HasIllegalCha
  at System.Security.Permissions.FileIOPermission.AddPathList(F
h)
  at System.Security.Permissions.FileIOPermission..ctor(FileIOP
  at System.IO.Path.GetFullPath(String path)
  at SourceForge.NAnt.Location.Init(String fileName, Int32 line
  at SourceForge.NAnt.Location..ctor(String fileName)
  at SourceForge.NAnt.Project.LoadBuildFile(String source)
  at SourceForge.NAnt.Project..ctor(String source)
  at SourceForge.NAnt.NAnt.Main(String[] args)

Please send bug report to [EMAIL PROTECTED]





_
MSN 8 with e-mail virus protection service: 2 months FREE* 
http://join.msn.com/?page=features/virus



---
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
___
Nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers