Calling C code from managed code

六月ゝ 毕业季﹏ 提交于 2019-12-04 10:22:38

If this is a simple C API then the most straight forward way to access it is using PInvoke. PInvoke was designed for exactly this scenario.

Could you post the signature of the C methods? If so we could provide the appropriate managed signatures.

EDIT

[DllImport("insert_the_dll_name_here")]
public static extern int new_game(ref double param1, ref double param2);

As Hans pointed out given the plural name of the parameters it seems possible these are arrays vs. single values. If so then the signature would need to change to account for that. For example if they are expected to be a predetermined fixed size the signature would look like the following

[DllImportAttribute("insert_the_dll_name_here"]
public static extern int M1(
  [MarshalAsAttribute(UnmanagedType.LPArray, ArraySubType=UnmanagedType.R8, SizeConst=5)] 
  double[] params1),
  [MarshalAsAttribute(UnmanagedType.LPArray, ArraySubType=UnmanagedType.R8, SizeConst=5)] 
  double[] params2) ;

As JaredPar states, this is the easiest way to do it - and indeed the designed way to do it.

Specifically, you'll need your option 2 and the .dll will need to be accessible (path wise) from your executable.

Since you need to deploy the C function in a separate DLL from your main C# program anyway, using C++/CLI is by far the easiest.

Do you have source code for the C functions? If so, you might be able to easily convert them into static member functions of a ref class. Then you can use the /clr:safe option and have pure managed code.

If you don't have source code, or the native code can't run as managed easily (uses lots of C runtime library functions, for instance), then you can build a wrapper or façade as you called it. The managed wrapper and native C code will end up together in the DLL which makes deployment easier, since the native DLL search path isn't involved.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!