Ok, letâs start with the basicsâ Which version of NAnt are you using? Could you provide a sample build file of your situation? Where is your build file stored in relation to the projects you are trying to build? Where are you executing NAnt? What command line are you using to execute NAnt? Can you provide with all the output of a sample run?
Iâve looked through the source code and I canât see anything right away that suggests that paths are being modified. I wondered at first whether you had spaces in your paths since that has gotten me a few times but your last example doesnât have spacesâ -- Edwin G. Castro Firing Systems Engineer [EMAIL PROTECTED]  ________________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Hara Sent: Sunday, April 18, 2004 11:43 PM To: [EMAIL PROTECTED] Subject: RE: [Nant-users] Long path bug? 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] Sent: Friday, April 16, 2004 6:51 PM To: Adrian Hara; [EMAIL PROTECTED] Subject: RE: [Nant-users] Long path bug? 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?... â ________________________________________ 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 â  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. áŠÄ5ë^™¨¥ŠË)¢{(ç[ÈL.)îÅ;¢¸š–ÁkyââžìmºÚ+‰©ië ž×o Ú'¥F†Û{ë"uéíjwBê éÓ‹^rè"zÂÞj¹Þêò¶§úè™û§u©žžÖ²Ú,ÊË^™§fŠx¬¶¶Š‰á¶Úý§l¢Çgr‰¿iØ×ôjYhr'wë(¥ÉbrCZžÛz»&j)bž b²ÓZžÛz»%ŠËl²‹«qç讧zØm¶›?þX¬¶Ë(º· ~ŠàzwþX¬¶ÏåŠËbú?©íºÇ
