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?

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.