RE: [Nant-users] Long path bug?

[Castro, Edwin Gabriel (Firing Systems Engr.)]

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 Sent: Friday, April 16, 2004 4:31 AM To: [EMAIL PROTECTED] Subject: RE: [Nant-users] Long path bug?     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] Sent: Thursday, April 15, 2004 7:35 PM To: Adrian Hara; [EMAIL PROTECTED] Subject: RE: [Nant-users] Long path bug?   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 <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 Sent: Thursday, April 15, 2004 5:42 AM To: [EMAIL PROTECTED] Subject: RE: [Nant-users] Long path bug?   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 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.