Hi Imran -

I suspect this may be due to Ninject expecting the referenced assemblies to be co-located with the project's output assembly, which isn't always the case under NCrunch. There's a page in the documentation that describes this problem and various ways that you can deal with it. If this doesn't work, do let me know and we'll dig a bit deeper and perhaps try something else.


Cheers,

Remco

As Ninject is a runtime framework, there is a high chance that other solutions exist that won't require the 'Copy referenced assemblies to workspace' setting to be enabled forcefully by the engine. Unfortunately I'm not personally familiar enough with the internals of Ninject or how it resolves assemblies to be certain of this, especially as I expect this is something that also changes between versions of Ninject and may depend on how the library is being used.

The 'Copy referenced assemblies to workspace' setting has a serious impact on the performance of NCrunch. When this setting is enabled, NCrunch will execute build chains in a similar manner to Visual Studio, instead of trying to shortcut the build system by building projects independently. This greatly increases the amount of build effort required before tests can be run, thus slowing down the engine. The setting should be considered an option of last resort rather than a default mode of operation. NCrunch will enable it automatically for setups that are known to have no way around it (such as when MSTest private method accessors are being used), but this is usually reserved for build-time frameworks rather than run-time ones.

Unfortunately this forum doesn't seem to let me rename the topic, though I'm sure others can still see the posts behind it. Most people show up here via google search anyway :)