Hi, thanks for posting!

NCrunch deliberately turns optimisations off when it builds your project, as the optimisations prevent it from accurately instrumenting the output assembly.

It's possible there may be another reason why your debug evaluations are not working.

Are you seeing code coverage data for this project? Does this affect just one solution, or all of them?

If the code coverage is working correctly, then this is probably related to the debugger (or PDB data) rather than optimisations. Is there a pattern around which values can be evaluated when you are in a debug session? Does the debug session correctly stop at breakpoints?

Regarding the RAM disk, the best advise I can give here is to increase the size of your RAM disk. Workspace consumption works similar to memory consumption in an application; it is possible (with serious effort) to limit it, but there will be a serious performance cost attached to this. NCrunch will already clean up workspaces religiously, so there shouldn't be a need to do this manually. Reducing the 'Max number of processing threads' will mean you won't get so many workspaces, but this will then make NCrunch run slower. When the goal of using a RAM disk is to improve performance, this would seem slightly self-defeating :)

It really depends upon the solution.

NCrunch can make several workspaces for each project in your solution, depending on your change patterns and the number of workspaces needed in parallel.

Because the workspaces are direct copies of the source of each project, large projects can consume quite a bit of space. If you're running out of space on the disk regularly, 4GB isn't enough for this solution.

Workspaces are always created to service build tasks. For this reason, it is unlikely for additional workspace space to be consumed at any time outside of NCrunch starting up builds (expect for tests that generate data on disk, but this is quite rare).

There really isn't anything that NCrunch can feasibly do here to limit its disk consumption. You either need to reduce the amount of concurrency through your settings, or you need to reduce the size of your projects on disk.