Erik,
This may be a strange request, and I'm sorry to bother you, but for some
reason I have had difficulty getting through to the Xerces list as of late.
If this fails to make it to the list, would you mind posting it for me?
Thanks,
Erik
---------------------------------------------
Perhaps MSDN articles
Q193462 - PRB: A Process Can Map 64 (or Less) Statically-linked CRT DLLs
Q118816 - PRB: Calling LoadLibrary() to Load a DLL That Has Static TLS
might be of help.
Make sure both the Xerces DLL and your DLL that uses Xerces are set to use
the correct CRT dlls (Debug Multithreaded DLL for debug builds or
Multithreaded DLL for release builds) in Project Settings | C/C++ tab |
Category: Code Generation | Use run-time library:.
This fixed a problem where VB6.EXE would not load a DLL (that statically
linked to the CRT) whilst debugging a VB app, but the app would load the DLL
just fine when run outside of the VB IDE...
-----Original Message-----
From: Erik Rydgren [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 18, 2001 9:44 AM
To: [EMAIL PROTECTED]
Subject: RE: Xerces and DLL?
Sensitivity: Private
Sorry I haven't answered earlier.
This error can depend on so many things. My suggestion is that you get
yourself a good C++ compiler and debugger. I use Visual studio myself. Build
the Xerces dll yourself and debug the code to find out exacly what the
problem is.
Sorry that I can't be of more help but the error is not very specific. It
can be anything.
Are you SURE the dll gets to the DllMain at all? Use the oldest trick in the
book. Put some Message boxes in your DllMain :), narrow the search until you
find it. But It requires that you build the DLL yourself.
Regards
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
