Home     |     .Net Programming    |     cSharp Home    |     Sql Server Home    |     Javascript / Client Side Development     |     Ajax Programming

Ruby on Rails Development     |     Perl Programming     |     C Programming Language     |     C++ Programming     |     IT Jobs

Python Programming Language     |     Laptop Suggestions?    |     TCL Scripting     |     Fortran Programming     |     Scheme Programming Language


 
 
Cervo Technologies
The Right Source to Outsource

MS Dynamics CRM 3.0

C# Programming

Novice question on interoperability


I need to write a C# DLL that is called from unmanaged C++ client.  I would
prefer not to use COM if I can (unnecessary overhead, time-sensitive
application).  Can somebody direct me at the tutorial or a sample?
Thank you.
Gregory
    If the client has to be completely unmanaged, then you are going to have
to export your component as a COM component.  It's a necessary overhead, as
it is the only way to access .NET components without keeping your code
unmanaged on the client side.

    Granted, you could use the CLI extensions in C++ to call .NET assemblies
directly, but then your client is no longer purely unmanaged.

--
          - Nicholas Paldino [.NET/C# MVP]
          - m@spam.guard.caspershouse.com

"Gregory Khra" <GregoryK@discussions.microsoft.com> wrote in message

news:2852AB52-0EF1-4B21-9AF4-CA2D05096E2E@microsoft.com...

Gregory Khra wrote:
> I need to write a C# DLL that is called from unmanaged C++ client.  I would
> prefer not to use COM if I can (unnecessary overhead, time-sensitive
> application).  Can somebody direct me at the tutorial or a sample?

I find it very hard to believe that the overhead of in process
COM calls should be measurable.

COM is the way to go.

Arne

Add to del.icio.us | Digg this | Stumble it | Powered by Megasolutions Inc