Re: [Nant-users] NANT and VS.NET CLI

[Ian MacLean]

Jean-Francois Gagnon wrote:

I would have thought that the <solution> tag and <project> tag would have
transparently used the VS.NET CLI... I see now that they don't and that the
process was rebuilt from scratch for VB and C# projects.
 

Yeah - the reason for this is so that you don't need to have vs.net on 
the build machine. Its also considerably faster than loading devenv.exe 
and dependencies each time.

Now, Fujitsu NETCobol is only available on the Windows platform... and NANT
is multi-platform.
 

That shouldn't cause any problems.

Implementing a new task for the compiler is one thing, but I would also like
to see the Solution and Project tasks handling the compiler as well... Is
this something that make sense?
 

sure. You'd need some extra code in the solution task and set it up so 
that it calls the cobol compiler task. As long as dependencies work the 
same way as for the 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 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 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