Re: Actions before DLLs are loaded?
"David Webber" <dave@musical-dot-demon-dot-co.uk> wrote in message
news:OBgcrFwoIHA.3900@TK2MSFTNGP05.phx.gbl...
But if you delay-load these DLL's as Alf suggests, then the DLL's are
loaded when the first exported function is called (which is after
CWinApp::InitInstance() is called).
It's a nice idea, but it surely can't be right!
I have (schematically) CexeApp derived from CDllApp derived from CWinApp
The constructor for CexeApp calls the constructor for CdllApp (exported
from one of my DLLs) which calls the constructor of CWinApp (exported from
the MFC DLL).
All this has surely happened by the time CWinApp::InitInstance() (which
itself must be exported from the MFC DLL?) is called.
Or am I missing something?
As Joe said, delay loading of whatever code executes before your
InitInstance() occurs does not good because it will be loaded before
InitInstance() regardless. This probably includes things like user, kernel,
mfc dll's, etc. But so what? These DLL's don't take too long to load
anyway. I thought you were happy to show your splash screen before *your
own DLL's* were loaded (which presumably take all the time to initialize).
Delay load these and it will work.
You can verify it yourself by delay loading your DLL's and set a breakpoint
in your InitInstance() and verify your DLL's are not shown as loaded in the
IDE Output window prior to the breakpoint being hit.
-- David