The answer for the GUI, other than changing output settings, was the addition of a Pre-Build Step

copy $(ProjectDir)..DebugBackingStore.* $(TargetDir)

测试项目的答案是在testrunconfig的部署选项卡中添加缺失的DLL。您可以通过直接编辑默认的LocalTestRun.testrunconfig（在解决方案项目下的解决方案项下显示）或右键单击解决方案并添加新的测试运行配置来执行此操作，然后它将显示在主测试菜单下。

感谢关于这个SO问题有关测试配置的答案，帮我找到了答案。

Are the C and C++ DLLs in the same directory as the C# assembly that s executing?

You may have to change your project output settings so that the C# assembly and the other DLLs all end up in the same folder.

I ve often used the Dependency Walker in cases like this; it s a sanity check that shows that all the dependencies can actually be found.

Once your app is running, you may also want to try out Process Monitor on the code you are running, to see which DLLs are being referenced, and where they are located.

The reason why this happens is because you either are loading DLLMAIN from managed code, before the CRT has an opportunity to be initialized. You may not have any managed code, be executed DIRECTLY or INDERECTLY from an effect of DllMain notifications. (See: Expert C++/CLI: .Net for Visual C++ Programmers, chapter 11++).

Or you have no native entrypoint defined wahtsoever, yet you have linked to MSVCRT. The CLR is automatically initialized for you with /clr, this detail causes a lot of confusion and must be taken into account. A mixed mode DLL actually delay loads the CLR through the use of hot-patching all of the managed entry point vtables in your classes.

A number of class initialization issues surround this topic, loader lock and delay loading CLR are a bit trickey sometimes. Try to declare global s static and do not use #pragma managed/unmanaged, isolate your code with /clr per-file.

If you can not isolate your code from the managed code, and are having trouble, (after taking some of these steps), you can also look towards hosting the CLR yourself and perhaps going through the effort of creating a domain manager, that would ensure your fully "in-the-loop" of runtime events and bootstrapping.

This is exactally why, it has nothting todo with your search path, or initialization. Unfortunately the Fusion log viewer does not help that much (which is the usual place to look for .NET CLR assembly binding issues not dependency walker).

Linking statically has nothing todo with this either. You can NOT statically link a C++/CLI application which is mixed mode.

1. Place your DLLMAIN function into a file by itself.
2. Ensure that this file does NOT have /CLR set in the build options (file build options)
3. Make sure your linking with /MD or /MDd, and all your dependencies which you LINK use the exact same CRT.
4. Evaluate your linker s settings for /DEFAULTLIB and /INCLUDE to identify any possiable reference issues, you can declare a prototype in your code and use /INCLUDE to override default library link resolution.

Good luck, also check that book it s very good.

Make sure the target system has the correct MS Visual C runtime, and that you are not accidentally building the C dll with a debug runtime.

This is an interesting dilemma. I ve never heard of a problem loading native .DLLs from C++/CLI after a call into it from C# before. I can only assume the problem is as @Daniel L suggested, and that your .DLL simply isn t in a path the assembly loader can find.

If Daniel s suggestion doesn t work out, I suggest you try statically linking the native C code to the C++/CLI program, if you can. That would certainly solve the problem, as the .DLL would then be entirely absorbed into the C++/CLI .DLL.

Had the same problem switching to 64-bit Vista. Our application was calling Win32 DLLs which was confusing the target build for the application. To resolve it we did the following:

1. Go to project properties;
2. Select Build tab;
3. Change Platform target: option to x86;
4. Rebuild the application.

When I re-ran the application it worked.