Re: [Ndoc-users] File Name Too Long?

[Gregory W. <gre...@pu...>]

Ben,
=20
Actually, the exception is one built in to the .net Framework.
=20
As for how to get around it, are you able to provide a shortened path
(e.g. C:\Progra~1 instead of C:\Program Files). I've never used
CruiseControl, so don't know whether this can be done.
=20
Also, does CruiseControl have any verbose logging options which may
print the full path of each folder / file that it's building? If so, you
could enable this and see where it runs into the exception.
=20
Gregory

________________________________

From: ndo...@li...
[mailto:ndo...@li...] On Behalf Of Benjamin
Wang
Sent: 29 August 2006 17:06
To: ndo...@li...
Cc: Allen Law
Subject: [Ndoc-users] File Name Too Long?



=20

I got a CruiseControl exception saying file name too long, as
CruiseControl has built-in length limits on file/directory name (260 and
248 respectively). Anyone knows how to get around this constraint? Or
how to find out which file names are too long?

=20

8/29/2006 10:41:30 AM: [MasterBuild:Info]: Build complete: Success

8/29/2006 10:41:36 AM: [MasterBuild:Error]: Publisher threw exception:
System.IO.PathTooLongException: The specified path, file name, or both
are too long. The fully qualified file name must be less than 260
characters, and the directory name must be less than 248 characters.

   at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)

   at System.IO.Path.GetFullPathInternal(String path)

   at System.IO.File.InternalCopy(String sourceFileName, String
destFileName, Boolean overwrite)

   at System.IO.FileInfo.CopyTo(String destFileName, Boolean overwrite)

   at
ThoughtWorks.CruiseControl.Core.Publishers.BuildPublisher.recurseSubDire
ctories(DirectoryInfo srcDir, DirectoryInfo destination)

=20

=20

=20

Thanks a lot for help!