At a bare minimum you could use the exec task to call either devenv or the cobol command line compiler.
For tighter integration you would need to implement a custom task to wrap the compiler. That isn't so hard to and there are plenty of examples in the nant code base if you decide to take that route.
Ian
Jean-Francois Gagnon wrote:
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 wrote:
Hi,
Is NANT rigged to invoke the VS.NET CLI transparently?
I am asking this because here we are using a COBOL Compiler (don't laugh) that VS.NET handles, but NANT does not (at least directly).
Regards
JFG
--
Ian MacLean, Developer, ActiveState, a division of Sophos
http://www.ActiveState.com
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
