Question

Hi we have a c++ project (library) which has to exposed to .net languages or may be other languages (old vb for example but this is not very important). Two options are write COM wrapper for the project or managed c++ wrapper. Which one to choose?

One great advantage, for example, of using manged c++ is using .net collections classes to pass as a parameters instead of enormous complexity of collections in COM.

Answer 1

If you’re COM collections are enormously complex, you may want to rethink how you approach COM collection management. Totally different issue there, but that being said…

Your mention of old-VB not being very important is more critical to your answer than you may think. Old VB doesn’t speak .NET, but it does speak COM very well. If you foresee having to go that road, that is a major push to the COM side.

I’m not a fan-per’se of managed C++ only because it is about the most non-portable, hard-to-manage, hard to read dialect of the language you’ll likely ever encounter. However, if the core code in your library is simple enough, you could probably get it up and running in managed C++ with reasonable effort. The more dynamic the library is, the harder it will be to port to .NET management. However…

Once it is there, a COM wrapper can get you back to your COM clients like legacy VB without too many problems provided you took wise choices when doing the port and kept things easily wrappable along the way.

Thats about the most round-about way I can say (with great pain) managed C++ is likely your best option, but I would seriously gel on it before throwing down that gauntlet.