Geeks With Blogs
Solid development Don’t make excuses for code, let it speak for itself
Beware of a warning that may occur during a Team Build that indicates that a dependent project is missing in a solution. Note that the warning will not appear in the ErrorsAndWarnings.txt because that only reports the errors and warnings from compilation itself and not those specific to MSBuild.

The warning found in BuildLog.txt is:
SomeSolution.sln : Solution file warning MSB4051: Project {A88..DB} is referencing a project with GUID {756..6AA}, but a project with this GUID was not found in the .SLN file.

Usually nothing problematic happens and the code compiles correctly. If you're unlucky and the dependent project has not been build yet it will cause the build to fail. But if you are very unlucky the build may succeed, but some files are missing in the drop location. This may happen if the problematic solution is build near the end of the Team Build. In this case the compiler detects that the dependent assemblies are no longer needed (it uses the "obj\Release\ProjectName.csproj.FileListAbsolute.txt" to detect this) and deletes them. Posted on Tuesday, November 3, 2009 4:31 PM Team Build | Back to top


Comments on this post: Beware of MSBuild warnings about missing projects in a solution

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © martin | Powered by: GeeksWithBlogs.net