1

I have an experimental .net project which implements a custom DLL loader, implemented as an AssemblyResolve event handler. It works great except...

If the DLL being loaded is present in the same folder as the EXE, my custom event handler is bypassed.

Is there a way for my custom DLL loader to take precedence?

The chain of events might look like this:

  1. The EXE and core DLLs are loaded and run as normal.
  2. The code sets its custom handler as the primary DLL loader.
  3. Some other code needs to load a DLL. My custom code is called and a loaded Assembly object is returned.
  4. Some more code needs to load another DLL. My custom code is called but declines, returning a NULL Assembly object. The normal DLL loader then takes over.

Note: This question asks for a similar scenario but the answers explore a very different strategy that's not really applicable here.

Community
  • 1
  • 1
billpg
  • 3,195
  • 3
  • 30
  • 57
  • This doesn't work at all the way you hope it does. AssemblyResolve will only fire if the CLR cannot find the assembly by itself. If you want it to fire then you'll have to give it a harder time, a subdirectory is the simple approach. If you return null then the code will bomb, there's no "second try". – Hans Passant Dec 02 '15 at 18:50

0 Answers0