I made an MFC extension DLL, but I couldn't get it working on the
client application. Can somebody please tell me what I did wrong in
the procedure:

1. I started an MFC extension DLL project called "MyDll". I added a
class called "MyClass" and added the keyword AFX_EXT_CLASS in the
class declaration in the header file.

2. I built the project and copied the files "MyDll.dll" and
"MyDll.lib" to the client project folder.

3. In the client project settings, I added the file MyDll.lib in the
linker - input section.

4. I made a MyDll.h file with the line: class AFX_EXT_CLASS MyClass;

5. I used #include "MyDll.h" in the cpp files where I need MyClass.

With the above steps, I expect MyClass to be defined. But when I use
the imported class it gave me the error:

error C2079: 'CClientApp::myobject' uses undefined class 'MyClass'


Please advise.

"wanwan" <ericwan78@yahoo.com> wrote in message 
news:1177094836.742967.148600@l77g2000hsb.googlegroups.com...
> 4. I made a MyDll.h file with the line: class AFX_EXT_CLASS MyClass;
>
> 5. I used #include "MyDll.h" in the cpp files where I need MyClass.
>
> With the above steps, I expect MyClass to be defined. But when I use
> the imported class it gave me the error:
>
> error C2079: 'CClientApp::myobject' uses undefined class 'MyClass'
>

The compiler needs to see the entire class definition of MyClass for it to 
know what are the methods and member data the client can call.  Defining it

  class AFX_EXT_CLASS MyClass;

is not sufficient for compiling the client, e.g.:

    MyClass MyClassInstance;
    MyClassInstance.SomeMemberFunction();

because the compiler can't see SomeMemberFunction() is a member of MyClass.

-- David 

On 20 Apr 2007 11:47:16 -0700, wanwan <ericwan78@yahoo.com> wrote:

>I made an MFC extension DLL, but I couldn't get it working on the
>client application. Can somebody please tell me what I did wrong in
>the procedure:
>
>1. I started an MFC extension DLL project called "MyDll". I added a
>class called "MyClass" and added the keyword AFX_EXT_CLASS in the
>class declaration in the header file.

You should use your own macro instead of AFX_EXT_CLASS, because otherwise
your DLL won't be able to #include headers from another DLL that also uses
AFX_EXT_CLASS, i.e. one extension DLL won't be able to use another
extension DLL. Below is a message I've posted several times concerning the
right way to use __declspec: 

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. 

>2. I built the project and copied the files "MyDll.dll" and
>"MyDll.lib" to the client project folder.
>
>3. In the client project settings, I added the file MyDll.lib in the
>linker - input section.
>
>4. I made a MyDll.h file with the line: class AFX_EXT_CLASS MyClass;

This defines an incomplete type called MyClass. About all you can do with
it is use it to declare pointer and reference types.

>5. I used #include "MyDll.h" in the cpp files where I need MyClass.
>
>With the above steps, I expect MyClass to be defined. But when I use
>the imported class it gave me the error:
>
>error C2079: 'CClientApp::myobject' uses undefined class 'MyClass'

You need to #include the header that defines MyClass; IOW, you need to
#include the header that contains:

class AFX_EXT_CLASS MyClass
{
.... class definition
};

This means your DLL's header files (at least the ones that export things)
have to be available to the DLL clients. This gets to be a royal pain.
Typically I handle it all by defining my own "lib" and "include"
directories. In the project settings, I relocate the DLL output files to my
lib and rename them so they don't conflict, sort of like what MS does with
MFC42.DLL vs MFC42D.DLL and all the variants. Then I create subdirectories
in my "include" folder for each library and move their public headers
there. I add my "include" folder to the compiler's list and #include the
files with:

#include <libname/filename.h>

As for the .lib files, I add my "lib" directory to the linker's list and
use #pragma comment(lib) in the public DLL header files to select the right
libraries; this relieves me from having to add the libraries to each
project's linker settings. You can also add "lib" to the IDE's PATH list so
the DLL's will be available when you try to run your programs.

To tie all this together, I create a file "DeclSpec.h" for each DLL, and it
typically looks like this:

#pragma once

#ifdef COMPILING_X_DLL
#define X_EXPORT __declspec(dllexport)
#else
#define X_EXPORT __declspec(dllimport)
#endif

#ifndef COMPILING_X_DLL
#  ifdef _DEBUG
#     pragma comment(lib, "XD.lib")
#  else
#     pragma comment(lib, "X.lib")
#  endif
#endif

Then every public DLL header file #includes "DeclSpec.h" first thing. It
gets more complicated when you have static library variants, Unicode
versions, etc, but that's the basic pattern.

-- 
Doug Harrison
Visual C++ MVP

On Apr 20, 5:23 pm, "Doug Harrison [MVP]" <d...@mvps.org> wrote:
> On 20 Apr 2007 11:47:16 -0700, wanwan <ericwa...@yahoo.com> wrote:
>
> >I made an MFC extension DLL, but I couldn't get it working on the
> >client application. Can somebody please tell me what I did wrong in
> >the procedure:
>
> >1. I started an MFC extension DLL project called "MyDll". I added a
> >class called "MyClass" and added the keyword AFX_EXT_CLASS in the
> >class declaration in the header file.
>
> You should use your own macro instead of AFX_EXT_CLASS, because otherwise
> your DLL won't be able to #include headers from another DLL that also uses
> AFX_EXT_CLASS, i.e. one extension DLL won't be able to use another
> extension DLL. Below is a message I've posted several times concerning the
> right way to use __declspec:
>
> 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.
>
> >2. I built the project and copied the files "MyDll.dll" and
> >"MyDll.lib" to the client project folder.
>
> >3. In the client project settings, I added the file MyDll.lib in the
> >linker - input section.
>
> >4. I made a MyDll.h file with the line: class AFX_EXT_CLASS MyClass;
>
> This defines an incomplete type called MyClass. About all you can do with
> it is use it to declare pointer and reference types.
>
> >5. I used #include "MyDll.h" in the cpp files where I need MyClass.
>
> >With the above steps, I expect MyClass to be defined. But when I use
> >the imported class it gave me the error:
>
> >error C2079: 'CClientApp::myobject' uses undefined class 'MyClass'
>
> You need to #include the header that defines MyClass; IOW, you need to
> #include the header that contains:
>
> class AFX_EXT_CLASS MyClass
> {
> ... class definition
>
> };
>
> This means your DLL's header files (at least the ones that export things)
> have to be available to the DLL clients. This gets to be a royal pain.
> Typically I handle it all by defining my own "lib" and "include"
> directories. In the project settings, I relocate the DLL output files to my
> lib and rename them so they don't conflict, sort of like what MS does with
> MFC42.DLL vs MFC42D.DLL and all the variants. Then I create subdirectories
> in my "include" folder for each library and move their public headers
> there. I add my "include" folder to the compiler's list and #include the
> files with:
>
> #include <libname/filename.h>
>
> As for the .lib files, I add my "lib" directory to the linker's list and
> use #pragma comment(lib) in the public DLL header files to select the right
> libraries; this relieves me from having to add the libraries to each
> project's linker settings. You can also add "lib" to the IDE's PATH list so
> the DLL's will be available when you try to run your programs.
>
> To tie all this together, I create a file "DeclSpec.h" for each DLL, and it
> typically looks like this:
>
> #pragma once
>
> #ifdef COMPILING_X_DLL
> #define X_EXPORT __declspec(dllexport)
> #else
> #define X_EXPORT __declspec(dllimport)
> #endif
>
> #ifndef COMPILING_X_DLL
> #  ifdef _DEBUG
> #     pragma comment(lib, "XD.lib")
> #  else
> #     pragma comment(lib, "X.lib")
> #  endif
> #endif
>
> Then every public DLL header file #includes "DeclSpec.h" first thing. It
> gets more complicated when you have static library variants, Unicode
> versions, etc, but that's the basic pattern.
>
> --
> Doug Harrison
> Visual C++ MVP

so is it required to export the default constructer/destructer for the
client application to instantiate class objects?

On 20 Apr 2007 15:22:31 -0700, wanwan <ericwan78@yahoo.com> wrote:

>so is it required to export the default constructer/destructer for the
>client application to instantiate class objects?

All functions your DLL client calls must be exported. For member functions,
this happens automatically when you export the whole class. The compiler
will generate the default ctor, dtor, copy ctor, and assignment operator
per the language rules as needed, so if you want to keep them in your DLL,
you need to define and implement the ones you want clients to be able to
use. To prevent their use, you can declare them private but not define
them, which is the standard way to prevent the default functions from being
generated and to turn their use into compile or link-time errors.

-- 
Doug Harrison
Visual C++ MVP

See below...
On 20 Apr 2007 11:47:16 -0700, wanwan <ericwan78@yahoo.com> wrote:

>I made an MFC extension DLL, but I couldn't get it working on the
>client application. Can somebody please tell me what I did wrong in
>the procedure:
>
>1. I started an MFC extension DLL project called "MyDll". I added a
>class called "MyClass" and added the keyword AFX_EXT_CLASS in the
>class declaration in the header file.
>
>2. I built the project and copied the files "MyDll.dll" and
>"MyDll.lib" to the client project folder.
>
>3. In the client project settings, I added the file MyDll.lib in the
>linker - input section.
>
>4. I made a MyDll.h file with the line: class AFX_EXT_CLASS MyClass;
*****
So right there, you have made a serious error.  You have declared that there is a class
called MyClass, AND YOU HAVE SAID NOTHING MORE ABOUT IT!  This is a "forward"
declaration, wherein you promise to say something later.
*****
>
>5. I used #include "MyDll.h" in the cpp files where I need MyClass.
>
>With the above steps, I expect MyClass to be defined. But when I use
>the imported class it gave me the error:
>
>error C2079: 'CClientApp::myobject' uses undefined class 'MyClass'
*****
You get this error because it IS an undefined class.  You promised to say something about
it later, and never did, so there is no possible way for the compiler to know what the
class does.  It does not know what size it is, what members it has, or anything other than
its name (of course, had you wanted to give a meaningful error message, you would have
shown the line that this erorr complains about.  It would be obvious; it would be a
declaration of a MyClass variable, or an attempt to use any method or access any member of
the class).

Your .h file must contain the entire class declaration.  If you do not want the
implementation visible, then the .h file declares the class, and your implementation will
declare a derived subclass of that class.
					joe
*****
*****
>
>
>Please advise.
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm

On Apr 22, 1:03 pm, Joseph M. Newcomer <newco...@flounder.com> wrote:
> See below...
> On 20 Apr 2007 11:47:16 -0700, wanwan <ericwa...@yahoo.com> wrote:
>
> >I made an MFC extension DLL, but I couldn't get it working on the
> >client application. Can somebody please tell me what I did wrong in
> >the procedure:
>
> >1. I started an MFC extension DLL project called "MyDll". I added a
> >class called "MyClass" and added the keyword AFX_EXT_CLASS in the
> >class declaration in the header file.
>
> >2. I built the project and copied the files "MyDll.dll" and
> >"MyDll.lib" to the client project folder.
>
> >3. In the client project settings, I added the file MyDll.lib in the
> >linker - input section.
>
> >4. I made a MyDll.h file with the line: class AFX_EXT_CLASS MyClass;
>
> *****
> So right there, you have made a serious error.  You have declared that there is a class
> called MyClass, AND YOU HAVE SAID NOTHING MORE ABOUT IT!  This is a "forward"
> declaration, wherein you promise to say something later.
> *****
>
> >5. I used #include "MyDll.h" in the cpp files where I need MyClass.
>
> >With the above steps, I expect MyClass to be defined. But when I use
> >the imported class it gave me the error:
>
> >error C2079: 'CClientApp::myobject' uses undefined class 'MyClass'
>
> *****
> You get this error because it IS an undefined class.  You promised to say something about
> it later, and never did, so there is no possible way for the compiler to know what the
> class does.  It does not know what size it is, what members it has, or anything other than
> its name (of course, had you wanted to give a meaningful error message, you would have
> shown the line that this erorr complains about.  It would be obvious; it would be a
> declaration of a MyClass variable, or an attempt to use any method or access any member of
> the class).
>
> Your .h file must contain the entire class declaration.  If you do not want the
> implementation visible, then the .h file declares the class, and your implementation will
> declare a derived subclass of that class.
>                                         joe
> *****
> *****
>
> >Please advise.
>
> Joseph M. Newcomer [MVP]
> email: newco...@flounder.com
> Web:http://www.flounder.com
> MVP Tips:http://www.flounder.com/mvp_tips.htm

My impression is that the class MyClass is loaded from the DLL after I
specify the library file in linker.
In my test program, MyClass has no member function or member
variable.  I thought I would start to add them after I get the DLL
working.

If I'm supposed to give the details of MyClass in source code, what's
the point of building a DLL?

You are confusing code loading strategy with compilation strategy; they are only vaguely
related.  While it is true that the CODE that IMPLEMENTS the class is not loaded until
runtime, the compiler still has to know about the class and all its methods, members, its
size, etc., AT COMPILE TIME or it can't connect to that code.
					joe

On 22 Apr 2007 15:22:53 -0700, wanwan <ericwan78@yahoo.com> wrote:

>On Apr 22, 1:03 pm, Joseph M. Newcomer <newco...@flounder.com> wrote:
>> See below...
>> On 20 Apr 2007 11:47:16 -0700, wanwan <ericwa...@yahoo.com> wrote:
>>
>> >I made an MFC extension DLL, but I couldn't get it working on the
>> >client application. Can somebody please tell me what I did wrong in
>> >the procedure:
>>
>> >1. I started an MFC extension DLL project called "MyDll". I added a
>> >class called "MyClass" and added the keyword AFX_EXT_CLASS in the
>> >class declaration in the header file.
>>
>> >2. I built the project and copied the files "MyDll.dll" and
>> >"MyDll.lib" to the client project folder.
>>
>> >3. In the client project settings, I added the file MyDll.lib in the
>> >linker - input section.
>>
>> >4. I made a MyDll.h file with the line: class AFX_EXT_CLASS MyClass;
>>
>> *****
>> So right there, you have made a serious error.  You have declared that there is a class
>> called MyClass, AND YOU HAVE SAID NOTHING MORE ABOUT IT!  This is a "forward"
>> declaration, wherein you promise to say something later.
>> *****
>>
>> >5. I used #include "MyDll.h" in the cpp files where I need MyClass.
>>
>> >With the above steps, I expect MyClass to be defined. But when I use
>> >the imported class it gave me the error:
>>
>> >error C2079: 'CClientApp::myobject' uses undefined class 'MyClass'
>>
>> *****
>> You get this error because it IS an undefined class.  You promised to say something about
>> it later, and never did, so there is no possible way for the compiler to know what the
>> class does.  It does not know what size it is, what members it has, or anything other than
>> its name (of course, had you wanted to give a meaningful error message, you would have
>> shown the line that this erorr complains about.  It would be obvious; it would be a
>> declaration of a MyClass variable, or an attempt to use any method or access any member of
>> the class).
>>
>> Your .h file must contain the entire class declaration.  If you do not want the
>> implementation visible, then the .h file declares the class, and your implementation will
>> declare a derived subclass of that class.
>>                                         joe
>> *****
>> *****
>>
>> >Please advise.
>>
>> Joseph M. Newcomer [MVP]
>> email: newco...@flounder.com
>> Web:http://www.flounder.com
>> MVP Tips:http://www.flounder.com/mvp_tips.htm
>
>My impression is that the class MyClass is loaded from the DLL after I
>specify the library file in linker.
>In my test program, MyClass has no member function or member
>variable.  I thought I would start to add them after I get the DLL
>working.
>
>If I'm supposed to give the details of MyClass in source code, what's
>the point of building a DLL?
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm

On Apr 22, 10:01 pm, Joseph M. Newcomer <newco...@flounder.com> wrote:
> You are confusing code loading strategy with compilation strategy; they are only vaguely
> related.  While it is true that the CODE that IMPLEMENTS the class is not loaded until
> runtime, the compiler still has to know about the class and all its methods, members, its
> size, etc., AT COMPILE TIME or it can't connect to that code.
>                                         joe
>
> On 22 Apr 2007 15:22:53 -0700, wanwan <ericwa...@yahoo.com> wrote:
>
>
>
> >On Apr 22, 1:03 pm, Joseph M. Newcomer <newco...@flounder.com> wrote:
> >> See below...
> >> On 20 Apr 2007 11:47:16 -0700, wanwan <ericwa...@yahoo.com> wrote:
>
> >> >I made an MFC extension DLL, but I couldn't get it working on the
> >> >client application. Can somebody please tell me what I did wrong in
> >> >the procedure:
>
> >> >1. I started an MFC extension DLL project called "MyDll". I added a
> >> >class called "MyClass" and added the keyword AFX_EXT_CLASS in the
> >> >class declaration in the header file.
>
> >> >2. I built the project and copied the files "MyDll.dll" and
> >> >"MyDll.lib" to the client project folder.
>
> >> >3. In the client project settings, I added the file MyDll.lib in the
> >> >linker - input section.
>
> >> >4. I made a MyDll.h file with the line: class AFX_EXT_CLASS MyClass;
>
> >> *****
> >> So right there, you have made a serious error.  You have declared that there is a class
> >> called MyClass, AND YOU HAVE SAID NOTHING MORE ABOUT IT!  This is a "forward"
> >> declaration, wherein you promise to say something later.
> >> *****
>
> >> >5. I used #include "MyDll.h" in the cpp files where I need MyClass.
>
> >> >With the above steps, I expect MyClass to be defined. But when I use
> >> >the imported class it gave me the error:
>
> >> >error C2079: 'CClientApp::myobject' uses undefined class 'MyClass'
>
> >> *****
> >> You get this error because it IS an undefined class.  You promised to say something about
> >> it later, and never did, so there is no possible way for the compiler to know what the
> >> class does.  It does not know what size it is, what members it has, or anything other than
> >> its name (of course, had you wanted to give a meaningful error message, you would have
> >> shown the line that this erorr complains about.  It would be obvious; it would be a
> >> declaration of a MyClass variable, or an attempt to use any method or access any member of
> >> the class).
>
> >> Your .h file must contain the entire class declaration.  If you do not want the
> >> implementation visible, then the .h file declares the class, and your implementation will
> >> declare a derived subclass of that class.
> >>                                         joe
> >> *****
> >> *****
>
> >> >Please advise.
>
> >> Joseph M. Newcomer [MVP]
> >> email: newco...@flounder.com
> >> Web:http://www.flounder.com
> >> MVP Tips:http://www.flounder.com/mvp_tips.htm
>
> >My impression is that the class MyClass is loaded from the DLL after I
> >specify the library file in linker.
> >In my test program, MyClass has no member function or member
> >variable.  I thought I would start to add them after I get the DLL
> >working.
>
> >If I'm supposed to give the details of MyClass in source code, what's
> >the point of building a DLL?
>
> Joseph M. Newcomer [MVP]
> email: newco...@flounder.com
> Web:http://www.flounder.com
> MVP Tips:http://www.flounder.com/mvp_tips.htm

I understood that part. I'm not sure if you read me previous message.
The MyClass class that I put into the DLL has no member variable or
member function. I made it for the purpose of trying it on the client
application because I'm new to DLL programming. Since it's an "empty"
class , I'd think the only line needed in the header is:

class AFX_EXT_CLASS MyClass;
or
class __declspec(dllimport) MyClass;

After I code the client application with the DLL, I should be able to
instantiate a MyClass object. I may be still missing some steps which
cause the error (please read above for my procedure.

Is there a good DLL tutorial that I can read on the internet? I tried
my best to follow some tutorials, but still no success.

No, you are still missing the point.  The declaration

class AFX_EXT_CLASS whatever;

says to the compiler, "I will tell you about this class in detail before you need it". You
never do tell it.  This is NOT the same as

class AFX_EXT_CLASS whatever {
};

which says "This is a class with no member variables and no methods".  The two concepts
are separate, and you cannot substitute the first form for the second form.  The first
form is a promise that the second form will appear later.  It allows you to do things like
declare pointers to the class, but it does not allow you to do anything BUT declare
pointers (or references) to the class.  The first time you do anything that requires
knowledge of the class, the compiler complains that you failed to tell it about the class
you promised to tell it about.
					joe

On 22 Apr 2007 23:26:06 -0700, wanwan <ericwan78@yahoo.com> wrote:

>On Apr 22, 10:01 pm, Joseph M. Newcomer <newco...@flounder.com> wrote:
>> You are confusing code loading strategy with compilation strategy; they are only vaguely
>> related.  While it is true that the CODE that IMPLEMENTS the class is not loaded until
>> runtime, the compiler still has to know about the class and all its methods, members, its
>> size, etc., AT COMPILE TIME or it can't connect to that code.
>>                                         joe
>>
>> On 22 Apr 2007 15:22:53 -0700, wanwan <ericwa...@yahoo.com> wrote:
>>
>>
>>
>> >On Apr 22, 1:03 pm, Joseph M. Newcomer <newco...@flounder.com> wrote:
>> >> See below...
>> >> On 20 Apr 2007 11:47:16 -0700, wanwan <ericwa...@yahoo.com> wrote:
>>
>> >> >I made an MFC extension DLL, but I couldn't get it working on the
>> >> >client application. Can somebody please tell me what I did wrong in
>> >> >the procedure:
>>
>> >> >1. I started an MFC extension DLL project called "MyDll". I added a
>> >> >class called "MyClass" and added the keyword AFX_EXT_CLASS in the
>> >> >class declaration in the header file.
>>
>> >> >2. I built the project and copied the files "MyDll.dll" and
>> >> >"MyDll.lib" to the client project folder.
>>
>> >> >3. In the client project settings, I added the file MyDll.lib in the
>> >> >linker - input section.
>>
>> >> >4. I made a MyDll.h file with the line: class AFX_EXT_CLASS MyClass;
>>
>> >> *****
>> >> So right there, you have made a serious error.  You have declared that there is a class
>> >> called MyClass, AND YOU HAVE SAID NOTHING MORE ABOUT IT!  This is a "forward"
>> >> declaration, wherein you promise to say something later.
>> >> *****
>>
>> >> >5. I used #include "MyDll.h" in the cpp files where I need MyClass.
>>
>> >> >With the above steps, I expect MyClass to be defined. But when I use
>> >> >the imported class it gave me the error:
>>
>> >> >error C2079: 'CClientApp::myobject' uses undefined class 'MyClass'
>>
>> >> *****
>> >> You get this error because it IS an undefined class.  You promised to say something about
>> >> it later, and never did, so there is no possible way for the compiler to know what the
>> >> class does.  It does not know what size it is, what members it has, or anything other than
>> >> its name (of course, had you wanted to give a meaningful error message, you would have
>> >> shown the line that this erorr complains about.  It would be obvious; it would be a
>> >> declaration of a MyClass variable, or an attempt to use any method or access any member of
>> >> the class).
>>
>> >> Your .h file must contain the entire class declaration.  If you do not want the
>> >> implementation visible, then the .h file declares the class, and your implementation will
>> >> declare a derived subclass of that class.
>> >>                                         joe
>> >> *****
>> >> *****
>>
>> >> >Please advise.
>>
>> >> Joseph M. Newcomer [MVP]
>> >> email: newco...@flounder.com
>> >> Web:http://www.flounder.com
>> >> MVP Tips:http://www.flounder.com/mvp_tips.htm
>>
>> >My impression is that the class MyClass is loaded from the DLL after I
>> >specify the library file in linker.
>> >In my test program, MyClass has no member function or member
>> >variable.  I thought I would start to add them after I get the DLL
>> >working.
>>
>> >If I'm supposed to give the details of MyClass in source code, what's
>> >the point of building a DLL?
>>
>> Joseph M. Newcomer [MVP]
>> email: newco...@flounder.com
>> Web:http://www.flounder.com
>> MVP Tips:http://www.flounder.com/mvp_tips.htm
>
>I understood that part. I'm not sure if you read me previous message.
>The MyClass class that I put into the DLL has no member variable or
>member function. I made it for the purpose of trying it on the client
>application because I'm new to DLL programming. Since it's an "empty"
>class , I'd think the only line needed in the header is:
>
>class AFX_EXT_CLASS MyClass;
>or
>class __declspec(dllimport) MyClass;
>
>After I code the client application with the DLL, I should be able to
>instantiate a MyClass object. I may be still missing some steps which
>cause the error (please read above for my procedure.
>
>Is there a good DLL tutorial that I can read on the internet? I tried
>my best to follow some tutorials, but still no success.
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm