TestDriven.NET and native C library
I am working on a C # application that makes calls to a native Windows C DLL. We are using TestDriven.NET with xUnit for testing. The problem is that whenever we run unit tests that use the C library (which we didn't write) and then try to build afterwards, a build error occurs about how the library is being used by another process. To fix this, you need to kill the TestDriven taskbar application that is left behind. We call the method that the library provides to free its memory, but it doesn't seem to help. Does anyone know how to stop this?
a source to share
We have the same problem as we create our own clr profiler. Oddly enough, Windows allows you to rename the dll, but not delete it.
The work around might be to create a pre-build step that renames the existing dll before building.
I also suggest that you contact Jamie Cansdale, the TD.NET author, and report this issue. He received a lot of support.
a source to share