I have an unmanaged C dll as part of my solution. When tests get run on the solution, it brings up the error

System.DllNotFoundException

Unable to load DLL ***** or one of it's dependents. The specified module could not be found (0x8007007e)

Is there a way to resolve this ?

I looked at "Copy referenced assemblies to workspace" but I couldnt find anything that looked like it would copy unmanaged dll's

Thanks for the reply.

That option only seems to let me specify other projects within the same solution. The dll I'm using is a 3rd party dll and isnt in a project.

Is there an option where I can copy a specific file into the NCrunch output folder ?

I don;t know how to do what you suggested. Do you have a link to somewhere that shows how ?

The code I'm having trouble with looks like this

private const string Dll = @"my.dll";

[DllImport(Dll, CallingConvention = CallingConvention.Cdecl, EntryPoint = "methodname")]
[MethodImpl(MethodImplOptions.ForwardRef)]
private unsafe static extern NINT methodname_();

public unsafe static NINT methodname()
{
return methodname_();
}

It cant find the dll. I event tried with a network path, which worked when run outside of NCrunch but not inside. It would appear that NCrunch must be running inside some type of sandbox that doesnt have access to the outside drives or network.

Placing the dll in the one of the folders in the system path didnt help either.

Ty setting the build action on the item to 'Content'. Set the 'Copy to output directory' setting to 'Copy always'. Make sure you add the native DLL to your test project, as this is the one that will be primarily hosted in the runtime environment. You can inspect the contents of the workspace by right-clicking on the failed build in the Tests Window an examining it in windows explorer. If things are configured right, MSBuild should treat the unmanaged DLL as a resource that is always copied adjacent to the test DLL when it builds the project. In this way, it sits in a resolution path for the code when the tests run.

You can find more information about NCrunch workspaces here.

Another option is to manually load the DLL inside your test code prior to it being needed, using Assembly.LoadFrom and specifying a path to the DLL. This is a bit messier as you need to be sure the code will always run before the DLL is needed (a SetUpFixture or equivalent might be the best option for this).