Printable View
Lost..... :( How do I call an unmanaged C++ DLL class member function from C# code? I can change any and all of these definitions. I just need to get a string from the C# world to the C++ world without pulling out the rest of my hair.
Using VS 2008
Unmanaged C++ Code in a DLL:
class MyClass
{
public:
bool Foo( char* str);
}
C# code that won't compile:
System.String test = "Hi there!";
MyClass c = new MyClass();
c.Foo( test );
Well, if the string will be modified from within the C++ dll you should pass in a StringBuilder. Anyhow, that does not seem to be your problem as you say your code does not compile. If that is the case, your function definition in C# is incorrect, so show us that.
Don't have one.
Why, you ask? Since I have included the DLL as a reference, I didn't think I needed a C# function definition. I'm calling all kinds of other functions from the DLL with no problem. If I leave out the string param or change it to an int, everything works as expected. It's just this string stuff that's stopping me.
Oh, and it won't be modified, just passed.
Disclosure: Long time C/C++ guy. Not a C# expert. Feel free to learn me. I'm all ears.
Thanks.
Could you include all relevant C# code? You're missing all the important bits...
I'm confused. What "important bits" am I missing? I thought I had included all that was needed, else I would have included the rest. Can you be more specific?
Thanks.
How about the compile error for starters?
Der... yeah. That would make sense:
Error The best overloaded method match for 'MyClass.MyClassClass.Foo(sbyte*)' has some invalid arguments
Error Argument '1': cannot convert from 'string' to 'sbyte*'
Pretty much everything ;)Quote:
Originally Posted by thumperj
Are you compiling your C++ as C++/CLI? How are you invoking the C++ function from C#. Whats the full class declaration in C# including the definition of the method you're calling. You've already provided the error which was also needed :) Can you also include the source for functions which you can call successfully?
Hmmm.... I guess I'm even more confused than I thought I was. I thought I had answered all those questions. Let me try again.
The C++ is unmanaged, which is what I thought meant it was not CLI. It's definitely not CLI. Just plain ol' C++.
I'm invoking the function from C# exactly like in the example in my original post. I new the object and call the function.
I don't have a class definition in C# for the C++ object. It's included as a Reference as the DLL. I never needed to put anything in the C# except "using MyClass;"
As for an example of functions I can call successfully, just take out the char* param in the C++ DLL function and the string param out of the C# code and I can call that same function all day. ;) In fact, change it all to an int and I can call it all day. It's the string parameter that's halting my progress.
If the DLL was written in "plain ol' C++" then you could only import functions using P/Invoke like soQuote:
Originally Posted by thumperj
Code:[DllImport("user32.dll")]
static extern IntPtr SendMessage(IntPtr hWnd, UInt32 msg, IntPtr wParam, ref POINT lParam);
Yes, ok. The /clr flag is set so it apparently does support CLR.
Instead of continuing the back and forth, I've created a simple example that demostrates the issue I'm trying to resolve. I've attached it to this thread.
Check out Form1.cs, line 27. Just uncomment the line and you'll see the compiler error.
Thanks for any direction.
just do a marshalling for the string parameter on the c# side like this and see :
Code:
[MarshalAs(UnmanagedType.LPStr)]System.String test = "Hi there!";
Thanks, vcdebugger. After your suggestion I've been off reading about MarshalAs. All new to me.
However, unless I've misunderstood or misplaced something, adding that to the code doesn't help with the compiler error referencing Foo:
>> Error: The best overloaded method match for 'MyClass.Class1.Foo(sbyte*)' has some invalid arguments
You can check out the attached zip file to see the error. It's all laid out nicely in the code, short, sweet and right to the point.
If you were calling an exported function from the DLL, you would use the PInvoke as described by Chris. However, since you want to execute a member function of a class inside your DLL, things may be a bit more complicated.
Basically, you can either compile your C++ DLL with /clr. Or, you have to create another C++/CLI DLL that wraps your native DLL in a .NET class. The mechanism is frequently referred to as "It Just Works" or "IJW". Generally in these wrapper DLLs, you have to marshal the data types manually. All in all, it can be a real pain the first time you do it.
This article seems to have the information you need. Be prepared, it's a long read:
http://www.codeproject.com/KB/mcpp/quickcppcli.aspx
Thanks, Night Wulfe.
So, my original claim was incorrect - the DLL *IS* being compiled with /clr. So, given that, any suggestions how I can just pass a string down to it?
I've posted a zip in one of the above posts with a simple sample project containing both a DLL and an application just like I've got showing the exact issue.
Thanks again.
Oh I see. The problem is you're trying to pass a string type to a char* (sbyte* to C#) type. These types are incompatible. There are two ways around this:
1) If you'd rather use the string type in C++ like you do C#, change your C++ DLL to take a type of System::String^ instead of char*. This will also require you to change your check against 0x00 (for null) to "nullptr" (without the quotes).
2) Alternatively, you'll have to proceed down the marshaling route mentioned before and/or use "unsafe" code blocks to get a byte array pointer to the string. This will probably require a call to System.Text.Encoding.ASCII.GetBytes.
Ok, so this has been a learning experience but I'll share how I've solved the issue in case anyone wanders into this thread. Of course, this is going to be pretty obvious to most people. It's certainly pretty obvious to me now. Live and learn.
Since the DLL I was calling into from C# was compiled /clr that means that I have access to the same basic data types in the C++ DLL code as I do in the C# app code. Thus, where I had:
MyClass:bool Foo( char* str);
I changed to:
MyClass:bool Foo( String ^str);
...and everthing magically worked.
If I didn't have access to the C++ DLL source code, I would have had to write, as Night Wulfe suggested, s C++/CLI wrapper around the native code.
Thanks for all the help, especially the links to learn more.
Night Wulfe, our posts passed in the ether. Thanks. I just figured out the solution you suggested.
Thanks again for the help.
In my opinion you are mismatching native vs. managed types and making your life more difficult.
If you are creating a managed C++ assembly to be used in a .Net application, then make your life easier by using managed types in the public methods.
So in your case, prototype Foo2 as:
Code:bool Foo2( String^ str );
That way, you can simply pass it a System.String object in the calling assembly:
Code:String str = "Test Me!";
myclass.Foo2( str );