other project types it shouldn't be too much effort
to put together.
Ian
Regards
JFG
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 15, 2004 8:36 AM
To: Jean-Francois Gagnon
Cc: [EMAIL PROTECTED]
Subject: Re: [Nant-users] NANT and VS.NET CL
Gagnon
Cc: [EMAIL PROTECTED]
Subject: Re: [Nant-users] NANT and VS.NET CLI
Sure - I know what CLI means. What wasn't clear was your meaning of
vs.net CLI. Do you mean calling vs.net itself via devenv.exe or do you
mean calling the individual compiler executables ( csc.exe etc ).
At a b
e
Yes, we are talking Fujitsu Cobol.
Regards
JFG
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 6:51 PM
To: Jean-Francois Gagnon
Cc: [EMAIL PROTECTED]
Subject: Re: [Nant-users] NANT and VS.NET CLI
Well VS.net only handles it because of
CLI stands for Command Line Interface
Yes, we are talking Fujitsu Cobol.
Regards
JFG
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 14, 2004 6:51 PM
To: Jean-Francois Gagnon
Cc: [EMAIL PROTECTED]
Subject: Re: [Nant-users] NANT and VS.NET CLI
Well VS.net only handles it because of the cobol language plugin ( its
by fujitsu isn't it ? ). Nant also requires some work - a cobol compiler
task to support cobol.
I'm not sure what you mean by vs.net CLI. You can call devenv.com with
the exec task if you need to.
Ian
Jean-Francois Gagnon w
No it doesn't. NAnt only uses the compilers that come with .NET Framework
(csc.exe, vbc.exe, and so on). It emulates the behaviour of VS.NET when
compiling projects through task.
Looks like another compiler needs to be added ;-)
Jarek
- Original Message -
From: "Jean-Francois Gagnon" <
