Hi, thanks for posting.

When it runs your tests, NCrunch will create a 'workspace' containing all your project files. This is essentially a sandbox in another area of your HDD. The project will be compiled in this workspace and any tests contained in it will also be run there. When the tests are run, NCrunch specifically sets the current directory to be the build output directory in the workspace.

The path you've given above seems to be malformed. This isn't referencing the NCrunch workspace (unless you've configured your workspace to something very strange), though the bottom three directories should normally exist in the workspace.

Note that when NCrunch sets the current directory, it does so at the start of the test run. If there is any code in any test that changes the current directory, NCrunch can't automatically set this back. This makes it possible for a test in your solution to 'corrupt' the current directory and cause downstream problems in your test run. The directory name you've described looks to me like it's been constructed by code making assumptions about the test environment that don't hold true under NCrunch. I recommend closely examining where this path came from as it seems to be that there is some complexity behind it.

See here for more information about workspacing - http://www.ncrunch.net/documentation/concepts_workspaces.

The only files that NCrunch itself will normally copy to _ncrunchreferences are the DLLs that are being statically referenced by your code. If you have other files under this directory, then these files won't be copied directly by NCrunch. It's possible you have a malfunctioning build step or custom code (perhaps a third party library) that is using the path of a statically referenced DLL as the drop-point for other related files. Turning on the 'Copy referenced assemblies to workspace' setting will turn off NCrunch's build optimisations here and may give you a workaround for the problem, but I would recommend trying to find the code responsible for copying those files. Although NCrunch is almost certainly executing this code, it isn't inside NCrunch's logic.

I'm also not sure if you intended for NCrunch's workspaces to be stored under C:\Data\LAS\Builds\Output\TestBin\Debug, as this doesn't seem right. If this is actually your workspace base path, you might want to change it to something more isolated - http://www.ncrunch.net/documentation/reference_global-configuration_workspace-base-path.