Build/Test Issues

Some projects show "Not built"

Started by georgedalessio on 6,957 views

I have one VS2013 solution with 10 projects and NCrunch only shows 6 and some of those are showing "Not Built" in the status column.
I couldn't find any answer to the "not built" questions in the forums. Can anyone clarify why Ncrunch shows a "not built" status and why not all the projects are showing (even though when resynchronizing it does go through all 10 projects and of course VS2013 build all 10 successfully).
I'm a new user and I'm using NCrunch version 2.13.0.5
Thanks
Hi, thanks for sharing this issue.

The most likely reason I can think that a project would be stuck in 'Not built' status is if a dependency was unable to build.

What can you tell me about the projects in this solution? Is there a pattern as to which projects NCrunch isn't detecting? Have any of these projects been customised or otherwise hand-coded in the build markup?
One of the projects that is not building has:
A file that has an relative address ..\..\..\Program Files %28x86%29\....\fileabc.xml (correct reference)
References to other projects in the solution like ..\ProjA\ProjA.ABC.csproj (correct references)
References to other Microsoft and 3rd.party like ..\packages\Microsoft... (correct references)
The NCrunch workspace has 6 folders (rather than the 10 for the solution).
Is there any file or debugging tool that can be used to see why NCrunch is not building some projects?
I'll start taking away dependencies until it builds but before doing that I'm trying to see if there are any way I can see what's going on.
Thanks
The relative reference to 'Program Files' needs to be corrected - this likely won't work properly inside the NCrunch workspace and it's also dangerous to have this in case the project files are ever moved or checked out to a different location. References to program files SDKs should be specified absolutely.

I recommend setting your 'Log Verbosity' to 'Detailed' and examining the Processing Queue Window to see if there are any further details around the projects. NCrunch normally reports build failures in the Tests Window, so if there aren't any details in there, some investigation/deduction will be needed.

Do you see all of your projects in the Tests Window if all of the filters are set to show them?

Make sure none of the projects are set to be ignored by NCrunch (using the 'Ignore this component completely' setting). It's also worth having a look at the common build problems to see if any of them may fit your situation.
I'll go through that and let you know.
Thanks

Post a reply

Log in to reply.