Hi.

I'm really new to this world of .Net so your help would be most
appreciated...

We have API and COM interfaces developed in c. We would also like to
supply a .net interface to our clients.

Searching - I found many new words :-) like .Net wrapper, Assembly...
but I couldn't find a clear cut answer -
What do I need to do in order to expose a .net interface?

What is the difference between "real" .NET APIs and having some kind of
wrapper around API or COM interface...?

Thanks in advance
Rakefet

(E-Mail Removed) wrote:
> We have API and COM interfaces developed in c. We would also like to
> supply a .net interface to our clients.
> What do I need to do in order to expose a .net interface?

Hi Rakefet. This is a common question. There are tools included with .NET
(tlbimp.exe) and Visual Studio (Add Reference->COM tab) to facilitate this
scenario. You can read more about using COM components from .NET at the
following URLs:

Interoperability of COM components with .NET
http://www.c-sharpcorner.com/Code/20...lityin.NET.asp

COM Interoperability in the .NET Framework
http://aspnet.4guysfromrolla.com/articles/010803-1.aspx

I hope this helps.
--
Derrick Coetzee, MCP, MSFT (Speech Server)
This posting is provided "AS IS" with no warranties, and confers no
rights.