Home/ Questions/Q 1109045
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T02:10:27+00:00

I’ve got the weirdest thing I’ve seen in a long while with VS2010. I

  • 0

I’ve got the weirdest thing I’ve seen in a long while with VS2010.
I have the same solution, checked out from svn, into two different folders.
One builds one doesn’t… but MSBuild doesn’t actual fail to build. All the assemblies build and it will run, but VS2010 keeps saying one project fails. If anyones seen this before or can see what I’m missing in my logs it would help heaps.

Looking closer at the second log, I read three “Build succeeded.” messages but a final “========== Build: 2 succeeded or up-to-date, 1 failed, 0 skipped ==========”. Go figure. There’s no post build events. I really don’t get this one.

------ Build started: Project: Data.Connection, Configuration: Debug Any CPU ------
Build started 23/09/2010 9:55:30 a.m..
Build succeeded.
Time Elapsed 00:00:00.02

------ Build started: Project: Common, Configuration: Debug Any CPU ------
Compile complete -- 0 errors, 0 warnings
Build succeeded.
Time Elapsed 00:00:01.12

------ Build started: Project: ClientA, Configuration: Debug Any CPU ------
Build started 23/09/2010 9:55:31 a.m..
Build succeeded.
Time Elapsed 00:00:02.14
========== Build: 3 succeeded or up-to-date, 0 failed, 0 skipped ==========

and

------ Build started: Project: Connection, Configuration: Debug Any CPU ------
Build started 23/09/2010 9:53:16 a.m..
Build succeeded.
Time Elapsed 00:00:00.03

------ Build started: Project: Common, Configuration: Debug Any CPU ------
Compile complete -- 0 errors, 0 warnings
Build started 23/09/2010 9:53:16 a.m..
Build succeeded.
Time Elapsed 00:00:00.87

------ Build started: Project: ClientA, Configuration: Debug Any CPU ------
Build started 23/09/2010 9:53:17 a.m..
Build succeeded.
Time Elapsed 00:00:01.95
========== Build: 2 succeeded or up-to-date, 1 failed, 0 skipped ==========
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    As a note for anyone else who comes across this, the actual problem was related to NTFS’s maximum path length.

    To explain further NTFS has a maximum length to a full path to a file (http://msdn.microsoft.com/en-us/library/aa365247.aspx). Our path structure was something along the lines of ( g:[…]\projects\Client\Client.Project\Client.Project.Library[…]. In short we blew out the maximum path length.

    Renaming some of the directory names resolved the issue.
    Just a shame that VS2010 couldn’t give a more reasonable error message / explanation.

    • 0