V1 Documentation
- Overview
- Guides
- Concepts
- Considerations And Constraints
- Absolute File References
- Assembly Colocation Assumptions
- Concurrent Use Of Test Resources
- Cross Application Domain Testing
- Heavily Executed Code Under Test
- Implicit File Dependencies
- Multi Threaded Tests
- Project Atomicity
- Project Build Platform And Configuration
- Test Atomicity
- Using NCrunch With Source Control
- Reference
- Global Configuration
- Overview
- Build Process Memory Limit
- Coverage Marker Style
- Cpu Cores Assigned To NCrunch Or Vs
- Fast Lane Threads
- Log To Output Window
- Logging Verbosity
- Marker Colours
- Max Number Of Processing Threads
- Max Test Runners To Pool
- NCrunch Tool Window Colors
- Performance Aggregation Type
- Performance Display Sensitivity
- Sliding Build Delay
- Spinner Colours
- Terminate Test Runners On Complete
- Test Process Memory Limit
- Use Hosted Task Runner
- Workspace Base Path
- Solution Configuration
- Project Configuration
- Overview
- Additional Files To Include
- Allow Dynamic Code Contract Checks
- Allow Static Code Contract Checks
- Analyse Line Execution Times
- Build Process Cpu Architecture
- Consider Inconclusive Tests As Passing
- Copy Referenced Assemblies To Workspace
- Default Test Timeout
- Ignore This Component Completely
- Include Static References In Workspace
- Instrument Output Assembly
- Ms Test Thread Apartment State
- Preload Assembly References
- Prevent Signing Of Assembly
- Proxy Process File Path
- Run Pre Or Post Build Events
- Use Build Configuration
- Use Build Platform
- Use Cpu Architecture
- Runtime Framework
- Global Configuration
- Troubleshooting
- Keyboard Shortcuts
- Manual Installation Instructions
Include Static References In Workspace
Project-level NCrunch configuration setting Default Value: TruePurpose
This configuration setting controls whether NCrunch will copy statically referenced assemblies into the _ncrunchreferences directory within project workspaces prior to the project being built.
When this setting is disabled, projects being built inside NCrunch workspaces will reach out of their workspace to reference assemblies in their original locations on disk.
Recommendations
Avoid disabling this configuration setting unless you are experiencing problems. Doing so will breach the isolation of NCrunch workspaces and can cause file locking problems throughout your foreground solution.

Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download