Hi, thanks for posting.

Unfortunately, the workspace behaviour is hard-built into the engine itself and cannot be disabled. Often people ask why this is the case. The reason is that it is impossible for NCrunch to reliably deliver on most of its features without using workspacing. NCrunch is a pre-build tool, in the sense that it works directly from your source code, not from compiled binaries. Its background nature means that it cannot safely share your foreground codebase with tools like Visual Studio, because there is simply too much interference from the IDE and other processes to allow it to perform work in this area. NCrunch also heavily manipulates the build system, output artifacts and runtime environment in a manner that does not play well with other tools, especially those that also attempt to take ownership of these areas and are changing on an almost monthly basis.

True and unconstrained background execution without some form of workspacing is unfortunately impossible. If it were feasible for me to provide a build of NCrunch without workspacing, I am fairly certain it is not a product you would consider worth using.

If you have customisations that prevent your projects from being built in the workspace, I recommend disabling these using MSBuild conditions (i.e. Condition="'$(NCrunch)' != '1'). NCrunch does also have a range of configuration options that are worth learning in detail as they can help with projects that don't like workspacing.