Hi, thanks for sharing this problem. I can see how this is happening in NCrunch and it should be easy to fix it, but this looks like a downstream problem from something else. This exception should only happen if you are running NCrunch over a solution with no projects able to be processed (i.e. all supported projects are ignored).

In theory, if/when I fix this problem, NCrunch will likely just complete its execution run and return no results. Does this match your expectation given the structure/configuration of your solution?

You may need to apply some deductive logic here so we can work out why the console tool won't load the projects. A few interesting things to check:

- Does the console tool also behave this way when used on the same solution on your dev machine?
- Does this happen only for a specific solution, or also others?
- Does it happen for a minimal dummy test solution?
- This may be harder to test (depending on your setup), but does this happen if the TeamCity server tries to open the solution in VS and process it using the NCrunch VS plugin?

Interesting ... How did this cause NCrunch to fail? Did it just fail to recognise all the projects in the solution? Or was it kicking up errors?

NCrunch itself no longer cares about global.json (earlier DNX integrated builds did), though I presume this file could have some affect on the build system, which NCrunch does use when trying to load projects. If the build system wasn't behaving as expected, it's possible NCrunch was dropping the projects as being unable to be loaded and then running into its unplanned explosion downstream. If this is the case, then fixing the downstream explosion you've originally reported here should allow the engine to progress further and report these problems in a more sensible way.