Accessing C++ through C#

[Harold Putman]

I have a C++ library that I want to be able to expose to C# clients. I expect
that I will have to created some kind of managed C++ wrapper in between the
two. I want the C# side to look very "natural" to C# developers. Are there
any guidelines for things like the best way to return strings, objects, and
collections of objects, etc... Should classic COM be involved in this in
any way?

[Peter Drayton]

Hi Harold,

You're on the right track - MC++ is good for this kind of thing, making it
quite easy to wrap a traditional C++ library in managed code. As for making
it easy to consume, I'd suggest you look at the rules for CLS compliance,
and make sure that the wrapper you expose follows those rules - it'll make
it easier for C# (and other language) clients to consume the class library.

As for using classic COM, it's another option, but I'd follow the MC++ route
first, since I'm guessing it'll be a lot faster to implement.

Regards,
Peter

"Harold Putman" <h.putman@ieee.org> wrote in message
news:3bb8be57$1@news.devx.com...
>
> I have a C++ library that I want to be able to expose to C# clients. I
expect
> that I will have to created some kind of managed C++ wrapper in between
the
> two. I want the C# side to look very "natural" to C# developers. Are there
> any guidelines for things like the best way to return strings, objects,
and
> collections of objects, etc... Should classic COM be involved in this in
> any way?
>
>