C＃Windows窗体无法在Windows10上加载不受管理的C ++ DLL

Question

I have a C# Windows Forms Application that use an unmanned c++ dll. When when I debug, or run it as standalone (on windows7), I just put the dll next to the app exe and it runs great.

When I try to do the same on Windows10 (run as standalone) I get the following exception:

Unable to load DLL 'AnalyzerLib.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)

Can anyone tell me why? should I give a permission somewhere or register it?

Here is how I access the dll from code:

namespace Analyzer {
public unsafe class Connector {
    [DllImport("AnalyzerLib.dll", CallingConvention = CallingConvention.Cdecl, SetLastError = true)]
    public static extern bool isAvailable();

    [DllImport("AnalyzerLib.dll", CallingConvention = CallingConvention.Cdecl, SetLastError = true)]
    public static extern void win32set_DetectParams(float[] parameters, int prob_Size);

    [DllImport("AnalyzerLib.dll", CallingConvention = CallingConvention.Cdecl, SetLastError = true)]
    public static extern void win32setDetectParamsAndColorMatrix(float[] parameters, int prob_Size, float[] colorMatrix16bytes);

    [DllImport("AnalyzerLib.dll", CallingConvention = CallingConvention.Cdecl, SetLastError = true)]
    public static extern void win32analyzeBuffer(byte[] javaBuffer, byte[] javaInputCopyBuffer, int[] analyzeBufferResArr, int width, int height, bool convertYUV2RGB);

    [DllImport("AnalyzerLib.dll", CallingConvention = CallingConvention.Cdecl, SetLastError = true)]
    public static extern int getCoreLogBufferSize();

    [DllImport("AnalyzerLib.dll", CallingConvention = CallingConvention.Cdecl, SetLastError = true)]
    private static extern byte* getCoreLogBuffer();

        }
}

Answer 1

If the DLL you are loading is in the same directory as the executable, then it will be found. Which leads us to conclude that the module(s) that cannot be found are your DLL's dependencies.

Normally this means that you need to install the appropriate MSVC runtime upon which your DLL depends.

• Make sure the you run the release version and not the debug

• You can figure out the dll dependencies by running from command prompted:

  dumpbin /DEPENDENTS my.dll