Remco;755 wrote:Usually if you have a build failure but no error, it means there's been an internal problem in NCrunch. The best thing you can do in this situation is go to have a look at the project in the processing queue. The queue will often have a much more physical view of the error. If you can copy/paste the error I should be able to help you resolve it.
[13:09:19.9684-BuildTask-37] ERROR (Internal): 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.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
at System.IO.Path.GetDirectoryName(String path)
at nCrunch.Core.WorkspaceManagement.WorkspaceBuilder.#=qenuhp10YEu8kK1QgmqfeyI5z15xX6MeUNNMLfaqP5Os=(SnapshotComponentMember #=qOSnhFnNu2kukizoT7OarUA==)
at nCrunch.Core.WorkspaceManagement.WorkspaceBuilder.#=qK7jczquFX4MYfgrhbJCOvwWUksgwBs4Fy$ip8_IoBBM=(IEnumerable`1 #=qO97dYaA_QYYbwNWwcFToMQ==)
at nCrunch.Core.WorkspaceManagement.WorkspaceBuilder.BuildWorkspaceForComponent(SnapshotComponent component, String workspacePath)
at nCrunch.Core.WorkspaceManagement.WorkspaceManager.GetWorkspaceForComponent(SnapshotComponent snapshotComponent)
at nCrunch.Core.BuildManagement.BuildEnvironment.Build(SnapshotComponent snapshotComponentToBuild, IList`1 referencedComponents)
at nCrunch.Core.BuildTask.DoProcessTaskAndReturnSuccessFlag()
at nCrunch.Core.Processing.ProcessingTask.ProcessTaskAndReturnSuccessFlag()
at nCrunch.Core.Processing.ProcessingQueue.#=q1dEw74QvFCHZvLaC0gI4_g==(ProcessingTask #=qQGKNQUwpcPIMHmMcq9HbgA==)
I think I read about this error. I should move ncrunch closer to the root right?