Hi Anees,

Thanks for sharing this issue.

Are there any warnings or build errors being shown by the engine? Would you be able to submit a bug report? The log file may be able to tell me if this is the result of an internal problem.

Hi Anees,

There is no built in limit on the maximum number of projects NCrunch can handle. It is regularly used with much more projects than 50. These are the possible things I can think of that may cause this to happen:

1. At least one of the projects has a 'Required capabilities' NCrunch project-level configuration option set which is preventing it from building
2. There is a strange dependency issue involving a project that NCrunch isn't able to build, and somehow the error isn't being reported
3. There is an internal problem

Would you be able to submit a bug report after you've had this happen to you? The log from the report will be able to help me narrow down the issue.

Hi Anees,

Just click the 'Submit bug report' option under the NCrunch VS menu.

Hi Anees,

Thanks for submitting the report. Note that there isn't any mechanism through which it is currently possible to track these reports from your side, but they do all get investigated so they are worth reporting.

The report showed some strange behaviour in your test environment, but nothing out of the ordinary around your build system.

I think it may be worth doing a full reset of your NCrunch cache data. If this doesn't work, I would suggest also resetting your configuration.

To reset the NCrunch cache data, close the solution (or VS), then look for a directory under your solution directory called _NCrunch_SOLUTIONNAME. Delete or rename this directory, then try re-opening the solution and enabling NCrunch.

To reset NCrunch's configuration, browse to your solution directory and perform a search for all .ncrunchproject files underneath all directories. Deleting these files along with the .ncrunchsolution file adjacent to your solution will clear all NCrunch configuration for the solution and will set you back to defaults. Make sure the solution is closed when you do this.

Thanks Anees.

The next thing, if you haven't tried this yet, is to set up compatibility mode in your configuration and see if this solves the problem.

Beyond this, troubleshooting becomes deductive. We need to find out what is different about the projects that are not being built. Most likely they have a dependency on a specific project that is experiencing a problem. It should be possible to identify this project by tracing up your build dependency tree until you find the lowest level project that isn't being built by the engine. Examine this project in detail - what does it depend on? Is there anything unusual about it? Does it make use of any build tools or configuration outside of the norm?