[Mono-dev] question regarding Mono PInvoke shared library loading behavior

Jb Evain jb at nurv.fr
Thu Jan 29 06:11:27 EST 2009


On 1/29/09, Koushik K. Dutta <koush at koushikdutta.com> wrote:
> I then have my Mono application also PInvoke into libmono. My assumption was
> that Mono would use the already loaded libmono, but instead, it seems to be
> loading a second copy. This is causing issues with my approach, because
> assumed I could use a couple global variables to set a couple callback
> pointers, but since two libraries are being loaded, this won't work.

What if you're trying to declare your pinvoke using `__Internal` for
the library as suggested by:



Jb Evain  <jb at nurv.fr>

More information about the Mono-devel-list mailing list