DLL forwarding is not the same as delay-loading

re: DLL forwarding is not the same as delay-loading

RyanBemrose — Mon, 04 Feb 2008 21:12:16 GMT

Just to be clear, does this behavior holds true when using actual delay-loading semantics? Which is to say that you can LoadLibrary(A.dll), but B.dll won't be loaded until you try to GetProcAddress(A!ForwardedFunction)?

re: DLL forwarding is not the same as delay-loading

nksingh — Tue, 05 Feb 2008 11:39:46 GMT

Sorry in advance for the bad joke, but I cannot resist:

"If bruteforce isn't working, then you just aren't using enough!"

re: DLL forwarding is not the same as delay-loading

I still intensely dislike Raymond (and I won't give him my name) — Thu, 07 Feb 2008 10:27:48 GMT

In your original post you said, "[T]he new DLL is not loaded unless somebody actually asks for the forwarded function from the old DLL."

That's a pretty vague way of describing the actual behavior; at the very least it admits of multiple interpretations. Accusing your readers if misreading something that's ambiguous is yet another example of your douche-tastic behavior.

re: DLL forwarding is not the same as delay-loading

GregM — Thu, 07 Feb 2008 22:27:03 GMT

If you dislike Raymond, then why the heck are you still here? Stop reading, and leave the rest of us to enjoy his blog in peace.