Jean-Francois Gagnon wrote:
I would have thought that the tag and 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 bui
I am talking devenv command line. The reason is that inter project
dependencies and the different compilers involved are taken care of,
including Fujitsu's Cobol compiler. In other words, some of our solutions
involve Cobol projects that are dependant on VB projects, etc.
I would have thought that
Adrian,
I’m not a Nant expert, but I wonder
if this is a problem with the vb.net compiler? Do you use Nant exclusively? Or
have you tried compiling your projects directly using the vb.net compiler or
VS.NET?
Not having looked at the Nant
task I expect that it doesn’t put a limit on
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 l
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
No answer? Nothing?... L
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Adrian Hara
Sent: Friday, April 09, 2004 5:21
PM
To: [EMAIL PROTECTED]
Subject: [Nant-users] Long path
bug?
Hello,
It’s my first time using a mailing list, and
also my first ti
