>Hi
>
[quoted text clipped - 11 lines]
>good). However, inside the code, the classes exported well using
>AFX_EXT_CLASS macro before the class name.
If Dependency Walker reveals the classes weren't exported, how is it they
"exported well inside the code"?
>There are two points to note
>here.
[quoted text clipped - 7 lines]
>feel the code is ok. It has something to do with some configuration
>setting. Can anyone guess?
The AFX_EXT_CLASS macro should be avoided, because it cannot be used in
multiple DLL scenarios, where one extension DLL uses another. Try replacing
your AFX_EXT_CLASS usage as follows:
In some DLL header file, which the other DLL headers #include, write the
following, replacing "X" with the name of your DLL, making sure it has a
reasonable chance of being unique:
#ifdef COMPILING_X_DLL
#define X_EXPORT __declspec(dllexport)
#else
#define X_EXPORT __declspec(dllimport)
#endif
Then #define COMPILING_X_DLL only in that DLL's project. This method can be
used by multiple DLLs, a big advantage over AFX_EXT_CLASS, and since the
macro names are unique, they don't conflict. Then you can do things like:
X_EXPORT void f();
class X_EXPORT MyClass
{
...
};
Look in the project's preprocessor options, and you may find the AppWizard
has already defined a suitable COMPILING_X_DLL macro for you.

Signature
Doug Harrison
Visual C++ MVP