dll import

[ric32br]

Hi all,


I have a c++ dll I have to call from c# using dll import but have no clue how to accomplish it. the c++ entry point is __declspec( dllexport ) UInt8 Update(unsigned char bForceUpdate). I am using this as a dll import

[DllImport("XbeeFW.dll", EntryPoint = "Update")]
public static extern bool fw(string c);

and call it as fw("TRUE") but get this error "A call to PInvoke function 'Puck Programmer!Puck.Main::fw' has unbalanced the stack. This is likely because the managed PInvoke signature does not match the unmanaged target signature. Check that the calling convention and parameters of the PInvoke signature match the target unmanaged signature."

Can some one please help a newbie get this to work?

TIA,

ric32br.

[Mutant_Fruit]

uint8 is an unsigned 8 bit integer, which in C# is a 'byte'. Unsigned char is the same as uint8 in this scenario, so the correct p/invoke signature is:

[DllImport("XbeeFW.dll", EntryPoint = "Update")]
public static extern byte fw(byte c);

There are alternative ways of implementing this, but this is the simplest and most direct. I assume a value of '0' is interpreted as false and anything else is true. Therefore you'd invoke it as:

byte result = fw (1); // passes 'true'
if (result == 0)
    Console.WriteLine ("Failure!");

[BigEd781]

You may also be running into a calling convention problem.

By default, your C++ apps will use the cdecl calling convention. However, C# defaults stdcall. So, check first, but if they aren't matched up you will need to change your native project or specify the calling convention in the C# signature:

[DllImport("XbeeFW.dll", EntryPoint = "Update", CallingConvention=CallingConvention.Cdecl)]

uint8 is an unsigned 8 bit integer, which in C# is a 'byte'. Unsigned char is the same as uint8 in this scenario, so the correct p/invoke signature is...

To be pedantic, sizeof(char) is guaranteed to be 1 by the standard, but it is not guaranteed to be 8 bits. So, uint8 is not necessarily the same as unsigned char on all platforms You are of course correct about the signature.

[ric32br]

Thanks, that did the trick.


ric32br.