Import C++ DLL into C#

[Michael Tissington]

I have a DLL written in C++. A number of the functions both expect a string
(BSTR) and also return a string (BSTR)

How do I define this in C# ?

[Nicholas Paldino [.NET/C# MVP]]

Michael,

Is this a regular C++ dll, or is it a COM dll? If it is, then you can
use the dll through COM interop (just adding the reference in VS.NET will do
it for you).

If it is not a COM dll, but rather a regular DLL with exported
functions, then you can declare the functions in C# code and call it through
the P/Invoke layer.

If neither of these cases apply, then you will need to change the (or
create another) DLL which will expose the functionality in those ways, or
create a managed code wrapper using C++/CLI.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Michael Tissington" <mt*********@newsgroup.nospamwrote in message
news:%2******************@TK2MSFTNGP02.phx.gbl...

>I have a DLL written in C++. A number of the functions both expect a string
(BSTR) and also return a string (BSTR)

How do I define this in C# ?

[Michael Tissington]

Its a regular DLL with exported functions ...
Where do I find information about the P/Invoke layer ?

[Tobias Funke]

Michael,

Here's a quick view at how P/Invoke works in C#:

http://msdn2.microsoft.com/en-us/lib...81(vs.71).aspx

But also I suggest you get some hands-on experience with P/Invoke by running
a few samples (such as from the Windows API). Here are some sample tutorials
that call unmanaged functions:

http://www.geekpedia.com/tutorial219...rom-Files.html
http://www.geekpedia.com/tutorial218...ng-Csharp.html
http://www.geekpedia.com/tutorial174...y-in-.NET.html

Do a couple of these cause once you learn how to use P/Invoke in C# you'll
never forget.

Regards,
Mr. T.

"Michael Tissington" <mt*********@newsgroup.nospamwrote in message
news:el****************@TK2MSFTNGP04.phx.gbl...

Its a regular DLL with exported functions ...
Where do I find information about the P/Invoke layer ?

[Michael Tissington]

Thanks - it turns out that I just needed to marshall the return value.
Something like ... AS <MarshalAs(UnmanagedType.AnsiBStr)String