Re: Managed c++ DLL call from C#
From: TheGurr (gurra_green.nospam_at_hotmail.com)
Date: 02/25/04
- Next message: Spaider: "Expose Guid as string"
- Previous message: Ola Sprauten: "Re: Managed c++ DLL call from C#"
- In reply to: Ola Sprauten: "Re: Managed c++ DLL call from C#"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Feb 2004 10:22:15 +0100
"Ola Sprauten" <osprauten@osiris.no_NO_SPAM> wrote in message
news:OSNYS13#DHA.2432@TK2MSFTNGP09.phx.gbl...
> The reason Intellisense finds it, is that nonmanaged c++ classes are all
> public by default. Where as a managed c++ class in by default private(or
> protected), so in you above example you need to add public before the
__gc.
Aaaaah! That did the trick! Thank you!
Strange that this is not mentioned in any of the "how to wrap your C++
code"-tutorials I've seen on the net (and I've done some surfing&searching).
Or I've been blind.
>
> You have to write a managed wrapper, I am pretty sure of that. Just have
to
> remember that manged c++ needs access modifiers(public, private and
> protected)
>
> Since all articles I've read have all said that you have to wrap unmanaged
> c++, I'd stick to that. There are probably some implications that I do not
> know of.
Exactly, better do it the safe way since that seems to be the general
advice. Will do some more experiments with calling code right away though
and see what happens.
- Next message: Spaider: "Expose Guid as string"
- Previous message: Ola Sprauten: "Re: Managed c++ DLL call from C#"
- In reply to: Ola Sprauten: "Re: Managed c++ DLL call from C#"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
