Easiest way to generate P/Invoke code?

I am an experienced .Net programer, but have not compiled a C/C++ program in my life. Now I have this C-dll, headers and documentation (3rd party, not from Win API), from which I need to call about ten methods.

I was thinking of using Platform Invoke. I found these three tools that would create the code for me:

• PInvoker: http://www.pinvoker.com
• P/Invoke Interop Assistant: http://www.codeplex.com/clrinterop
• P/Invoke Wizard: http://www.paulyao.com/res/pinvoke/pinvoke.aspx

and possibly

• Swig: http://www.swig.org/

Pinvoker seems to have a开发者_JAVA百科 bit different approach than the Interop assistant and the Wizard. Swig I just found when checking that this question has not been asked here.

What are the pros and cons of these tools?

What would be the best = easiest and safest way for me to produce the P/Invoke code given that I don't know much about C/C++?

---

See http://dotnetperls.com/dllimport-interop for an interop example, and this MSDN article for more info. The bible for this stuff is Adam Nathan's book.

Basically you will need to identify the functions in the DLL you want to call. These need to marked with extern to make them accessible to the outside world. The next step, which can get tricky is writing a DllImport for the function. This needs to map between the managed and unmanaged worlds. You will need to work out how to marshal any complex data structures from the C dll into managed code.

You should check to see if there is any sort of COM interface to the DLL. Make sure you really need to use P/Invoke first.

SWIG was originally for wrapping C/C++ code for use from scripting languages. It generates C# code from an interface description (see tutorial). I wouldn't recommend using it from C# if P/Invoke is an option.

---

if the signatures of the functions are simple then it should take 10 minutes to setup - ie if they take 2 char * and return an int. Its only once they get complicated that it gets messy

The bible on pinvoke is Adam Nathans - .NET and COM: The Complete Interoperability Guide

And I agree with other poster - swig is not the right thing