I asked some people in the .Net team about this. QCalls are calls to native methods within the CLR runtime. They behave like other [DllImport]s, but they’re faster because they make specific (undocumented) assumptions about what the native methods do, so they can skip various marshalling and GC and exception checks. InternalCall is different; it’s … Read more
You can embed the unmanaged DLL as a resource if you extract it yourself to a temporary directory during initialization, and load it explicitly with LoadLibrary before using P/Invoke. I have used this technique and it works well. You may prefer to just link it to the assembly as a separate file as Michael noted, … Read more
dumpbin from the Visual Studio command prompt: dumpbin /exports csp.dll Example of output: Microsoft (R) COFF/PE Dumper Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. Dump of file csp.dll File Type: DLL Section contains the following exports for CSP.dll 00000000 characteristics 3B1D0B77 time date stamp Tue Jun 05 12:40:23 2001 0.00 version 1 ordinal … Read more
Contrary to the suggestions by some of the other answers, using the DllImport attribute is still the correct approach. I honestly don’t understand why you can’t do just like everyone else in the world and specify a relative path to your DLL. Yes, the path in which your application will be installed differs on different … Read more