RE: [Nant-users] Path length problem with resgen

2004-08-10 Thread Troy Laurin
> The problem in your case might be that the path of that > temporary directory that we create exceeds the max. path > length. The ensure uniqueness of that temp directory, we > combine the temp path with a Guid : > > Path.Combine(Path.GetTempPath(), Guid.NewGuid().ToString("N", > CultureInfo

Re: [Nant-users] Path length problem with resgen

2004-08-10 Thread Gert Driesen
> - Original Message - > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Tuesday, August 10, 2004 9:30 AM > Subject: RE: [Nant-users] Path length problem with resgen > > Thanks for that Brian, > > I ha

RE: [Nant-users] Path length problem with resgen

2004-08-10 Thread Bill.Martin
nt: 09 August 2004 07:50 To: Bill Martin Cc: [EMAIL PROTECTED] Subject: [Nant-users] Path length problem with resgen Bill, It seems that your total path length may have exceeded the limit of 255 chars. One alternative is - when the src files are extracted to your local drive, consid

[Nant-users] Path length problem with resgen

2004-08-09 Thread Brian Yeo
Bill, It seems that your total path length may have exceeded the limit of 255 chars. One alternative is - when the src files are extracted to your local drive, consider fiddling the file/path name by making certain name shorter. eg Microsoft.ApplicationBlocks.ConfigurationManagement (CS) to conf

[Nant-users] Path length problem with resgen

2004-08-06 Thread Bill.Martin
I have just installed the latest nightly build and my build now doesn't work. It works fine with the previous version I had (0.85 build 05/04/2004). I've included the output from the old version of nant and the new one below. Anybody seen anything similar? I've run it with the verbose output on