|
I’ve tried creating a new project in
the same dir tree as the other projects, adding some really long name files and
compiling it. It works. But my other projects still don’t. I’ve
tried using <solution> instead of <vbc> and I get the same error
messages, in the likes of: Vbc:
Command line error BC2001 : file ‘c:\work\rsgi\devel’ could not be
found Notice how the error message truncates the
path, which is at least ‘c:\work\rsgi\development\conta\rsgiconta\’
for the solution I was building and on which it failed. Any ideas? From: Castro, Edwin
Gabriel (Firing Systems Engr.) [mailto:[EMAIL PROTECTED] So, the VB command line compiler works
fine… If I understand correctly the <vbc> task uses the VB command
line compiler… Maybe the task is really at fault. Like I said before
I’m not an expert on Nant code, but I will look through it and try to
determine how it calls the VB compiler. I’ll post any findings too you
and the mailing list! From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Adrian Hara VS.NET builds fine. I’ve tried the command line compiler
and it works fine too. I find it very strange that the
<csc> task should work fine, given that the c# parts of the project are
in the same directory structure, with maybe even longer paths. No clue… From: Castro, Edwin
Gabriel (Firing Systems Engr.) [mailto:[EMAIL PROTECTED] 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 <vbc>
task I expect that it doesn’t put a limit on the size of paths. That
makes me think that the vb.net compiler has this limitation and not the
<vbc> task… --Edwin From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Adrian Hara No answer? Nothing?... L From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Adrian Hara Hello, It’s my first time using a mailing list, and
also my first time using nant, so be gentle J My problem is as follows: I have a script to build some solutions. Some of them
c#, some of them vb.net. The problem is that, while building the c# solutions
works fine, the vb.net solutions build fails, with messages like: Vbc : Command
line error BC2001: file ‘<insert long path here>’ could not
be found From what I can gather, when the path to the filename
(including the filename) is more than 64 characters long, I get this error. If
I MOVE the solution from the dir with the long path to a dir like c:\test\ and
build it, it works perfectly fine. In fact, through trial and error (renaming
of the long dir progressively) I found the 64 characters limit. Also, from what I’ve seen, this problem arises
only with the <vbc> task, the <csc> tasks that build solutions in
the same long path work fine. Any input would be greatly appreciated, thanks. Ps: please don’t suggest I do a <solution>
instead of <vbc>. I can’t, because of a number of reasons which i
don’t think are relevant here. |
- [Nant-users] Long path bug? Adrian Hara
- RE: [Nant-users] Long pa... Adrian Hara
- RE: [Nant-users] Long pa... Castro, Edwin Gabriel (Firing Systems Engr.)
- RE: [Nant-users] Long pa... Adrian Hara
- RE: [Nant-users] Long pa... Castro, Edwin Gabriel (Firing Systems Engr.)
- RE: [Nant-users] Lon... Adrian Hara
- RE: [Nant-users] Long pa... Castro, Edwin Gabriel (Firing Systems Engr.)
- RE: [Nant-users] Long pa... Madhan Retnaswamy
