How are .module extern references in an assembly manifest resolved (aka how are libraries used in PInvoke resolved)

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Justin Rogers - 14 May 2004 05:25 GMT

I'm running into a case, where I replace the library within my directory (say I
put a custom gdiplus thunk library), but my library isn't getting loaded into
the process. Instead the actual gdiplus library is being loaded. Under normal
circumstances writing thunk libraries for debugging has been fairly easy, but
this is proving very difficult. Any clues?

Signature

Justin Rogers
DigiTec Web Consultants, LLC.
Blog: http://weblogs.asp.net/justin_rogers

Reply to this Message

Fabian Schmied - 14 May 2004 21:23 GMT

Justin Rogers schrieb:

> I'm running into a case, where I replace the library within my directory (say I
> put a custom gdiplus thunk library), but my library isn't getting loaded into
> the process. Instead the actual gdiplus library is being loaded. Under normal
> circumstances writing thunk libraries for debugging has been fairly easy, but
> this is proving very difficult. Any clues?

Wild guess: Because System.Drawing is based on GDI+, gdiplus.dll is
already loaded into the process and this loaded instance is used when
the .module extern reference is resolved.

Fabian

Reply to this Message

Rate this thread:

How are .module extern references in an assembly manifest resolved (aka how are libraries used in PInvoke resolved)

Free Magazines