NCover and Spring.NET depedency injection

Hello everyone,

We have a software system that uses the dependency injection features of Spring.NET to dynamically load some components based upon configuration files. We would like to introduce Code Coverage for our unit tests into our build. Currently we use TFS/MSTest for our build/testing but the TFS Code Coverage doesn't work with the Spring.NET mechanism (looks like it builds instrumented code into differently named assemblies and Spring.NET can no longer find the classes it needs).

Is NCover able to correctly provide coverage for systems that use Spring.NET dependency injection?

Thanks for you help

RE: NCover and Spring.NET depedency injection

NCover does not change the names of assemblies when doing instrumentation, so Spring.NET should not have that problem. We've not tested NCover with Spring.NET, so we can't speak to whether it works or not. I don't know of any reason why it wouldn't work. We routinely work with code that does dynamic assembly/code generation/loading.

Your best bet would be to download the trial version and try it out. NCover does support coverage of tests run under MSTest. Does Spring.NET work under MSTest?

Peter