Hi, thanks for posting and for your interest in NCrunch!

NCrunch should support solutions with many projects, although the initial load time may be higher than for smaller projects.

If NCrunch gets stuck during initialisation with no visible activity for more than 3 minutes, then most likely there has been an internal problem. Would you be able to submit a bug report when the initialisation has stopped? Hopefully this will give me the information I need to find the issue and provide you with a workaround or fix.


Cheers,

Remco

Thanks for submitting the bug report. It looks as though NCrunch is throwing OutOfMemoryExceptions when traversing the project relationships within your solution.

I've noted this down for review as part of the next minor release, as it's possible there is a resource consumption or performance issue that is being surfaced by the size of your solution structure.

I'm wondering if you may be able to try the following to see if this makes any difference:
- Ensure you have no other programs running on your machine other than Visual Studio
- Disable any background analysis tools you have inside Visual Studio that may increase memory consumption

For the project that is taking a long time to build, can you give me any indication of the size of this project? i.e. in times of lines of code or compiled assembly size? Does the project contain any large resource files?



Thanks!

Remco

I have a feeling that it may be impossible to have an optimal experience with NCrunch on a solution of this size, without selectively disabling large parts of it or making changes to your solution structure. I hope that NCrunch will be able to better support solutions of this size/structure in future as the tool matures, but for the time being I may be able to suggest a few things to help take the edge off the resource hogging:

- Assuming that your generated code is housed within its own project(s), consider removing the projects containing generated code from the solution itself and referencing this code using Assembly References instead of Project References. This will massively reduce the load placed on your IDE and tooling by the generated code, and NCrunch will simply treat it as referenced material rather than part of the solution.
- Consider suppressing code coverage and instrumentation for very large classes within your solution by using NCrunch's coverage suppression syntax. This will reduce the instrumentation overhead.
- As you've already done - turning off 'Instrument Output Assembly' for large projects will make a big difference to build times and performance in general
- If you have large non-critical projects included in your solution, try switching them off with the 'Ignore this project completely' configuration option


Cheers,

Remco

I tried this build but had to revert to previous version due to problems with build failures.

This was happening on my smaller solution that was working perfectly before the upgrade.

I sent in a bug report.

Basically what was happening was when I was changing code either in a unit test or application code NCrunch would try to rebuild and my test project would fail to build. I would have to reset ncrunch to get it building again, then next time I changed code, it would happen again.