I'm adding NCrunch to a new project (I changed jobs, so starting from scratch).
Initially, NCrunch had a lot of build errors, so I've been modifying the configuration to try and resolve them. When I change 'Infer project references using assembly names" to "True", NCrunch never fully loads and sits at the "Loading projects (37 of 36)" message. NOTE: that's not a typo.. it says it's loading the 37th of 36 projects.
This solution has a mixture of C#, C++ and VB.NET projects, if that matters.
Turning the "Infer.." setting back to "False" resolves the issue. Flip back to "True" and the issue returns.
FYI: I submitted a report from within Visual Studio referencing this forum post.
Remco NCrunch Developer
#8998
19 Jul 2016 23:45 UTC
Thanks for sending through the bug report.
This seems to be a downstream problem caused by one of the projects failing to load. Try turning off the setting and examining the list of load errors. One of these projects doesn't seem to have normal platform/configuration settings, see http://www.ncrunch.net/documentation/considerations-and-constraints_project-build-platform-and-configuration for more details on this.
I've implemented a fix for this that will be released in v2.24. To get this solution working immediately, I recommend fixing the project load failure.
As crazy as it looks, the 37/36 issue is actually by design. While NCrunch loads your projects, it also identifies any dependencies these projects may have on other projects outside the solution. NCrunch will then load these dependencies recursively, so it can actually load more projects than are listed in the solution.
This seems to be a downstream problem caused by one of the projects failing to load. Try turning off the setting and examining the list of load errors. One of these projects doesn't seem to have normal platform/configuration settings, see http://www.ncrunch.net/documentation/considerations-and-constraints_project-build-platform-and-configuration for more details on this.
I've implemented a fix for this that will be released in v2.24. To get this solution working immediately, I recommend fixing the project load failure.
As crazy as it looks, the 37/36 issue is actually by design. While NCrunch loads your projects, it also identifies any dependencies these projects may have on other projects outside the solution. NCrunch will then load these dependencies recursively, so it can actually load more projects than are listed in the solution.
Remco NCrunch Developer
#8999
20 Jul 2016 07:50 UTC
The fix for this issue is now available as part of v2.24.
Yes, there are definitely some non-normal platform/configuration settings in play. Thanks for looking into this. Love your product and it's become one of my primary dev tools!
Post a reply
Log in to reply.