Well finally something I feel qualified to comment on!
I'm not sure about C++ functions, but you can definitely call C functions which are exposed in DLLs using P/Invoke in .NET.  It's very simple - you just create a bunch of .NET functions which match the C function signatures, then you can use certain attributes for telling it which DLL the method is in and how to marshal the managed memory to unmanaged memory.  If you want a nice API it's best to design something that behaves more like a .NET component would ( e.g using delegates and event handlers rather than inheriting off the PropertyListener for notifications) which would take some work.
Anyway I can't possibly agree with Hugh's statement about C# being the same as VB!  It's much closer to C++/Java.  Maybe he meant that VB.NET and C# will both compile into the same MSIL code or something?

On 9/2/05, Reed Hedges <[EMAIL PROTECTED]> wrote:
On Thu, Sep 01, 2005 at 11:32:11PM +0200, Hugh Perkins wrote:
> What Peter said. I think. It's been a while :-)
> Random aside: I've been playing with .Net at work; it's kindof cool, though
> it's basically VB with a C++ syntactic sugar. I dunno why people claim that
> C# means the end of VB, since C# basically *is* VB. It's still pretty cool
> though :-)

Am I correct that it's no problem to call C++ code or link against a C++ library
from .net?  Would the C++ library (libvos for example :) need to be compiled
with CLR (".net extensions") enabled?


vos-d mailing list

vos-d mailing list

Reply via email to