I am wondering if someone found a work-around (other than making the path name shorter) for the "path too long" error when running Nant. Our directory structure may be two to three levels and we like to use descriptive names.
Here is the output I get that shows the error, just in case you have no idea what I am talking about (smile):
<<output.txt>>
Thanks!
NAnt version 0.8.3 Copyright (C) 2001-2003 Gerry Shaw http://nant.sourceforge.net
Buildfile: file:///C:/nextgenerationarchitecture.build
[echo] Build Debug Using Solution
[solution] Starting solution build.
Total time: 0 seconds.
BUILD FAILED
INTERNAL ERROR
System.IO.PathTooLongException: The path is too long after being fully qualified.
Make sure path is less than 260 characters.
at System.IO.Path.nGetFullPathHelper(String path, Char[] invalidPathChars, Char[]
whitespaceChars, Char directorySeparator, Char altDirectorySeparator, Char
volumeSeparator, Boolean fullCheck, String& newPath)
at System.IO.Path.GetFullPathInternal(String path)
at System.IO.FileInfo..ctor(String fileName)
at NAnt.VSNet.Tasks.Reference..ctor(Solution sln, ProjectSettings ps, XmlElement
elemReference, Task nanttask)
at NAnt.VSNet.Tasks.Project.Load(Solution sln, String strFilename)
at NAnt.VSNet.Tasks.Solution.LoadProjects()
at NAnt.VSNet.Tasks.Solution..ctor(String strSolutionFilename, ArrayList
alAdditionalProjects, ArrayList alReferenceProjects, TempFileCollection tfc, Task
nanttask)
at NAnt.VSNet.Tasks.SolutionTask.ExecuteTask()
at NAnt.Core.Task.Execute()
at NAnt.Core.Project.InitializeProjectDocument(XmlDocument doc)
at NAnt.Core.Project.Execute()
at NAnt.Core.Project.Run()
Please send bug report to [EMAIL PROTECTED]
