Re: CObject use?

From:

"Tom Serface" <tom.nospam@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Sun, 10 Jun 2007 07:52:53 -0700

Message-ID:

<uR5gX82qHHA.4768@TK2MSFTNGP02.phx.gbl>

Bryan,

I agree with David. If you want to use the MFC classes the best way to do
it is to make your project an MFC project. You can make several kinds of
MFC projects using the creation wizards and they will create the initial
files with the proper headers. It will make your life a lot easier and may
even make sense for you to start over with the wizard code even if just to
see what it creates for you.

Tom

"Bryan" <bryan@no.spam.com> wrote in message
news:ToMai.7488$u56.9@newssvr22.news.prodigy.net...

Bryan:

CObject is an MFC class. If you create an MFC app using the wizard and
look in stdafx.h you will see which includes are needed. An MFC app does
not (must not) include windows.h directly, but it gets included in the
proper way by the MFC headers.

So I don't include windows.h directly, but I do include stdafx.h...

How does this work? I have a static lib that is build using mfc in a
shared dll. I removed all instances of '#include "stdafx.h"' from my
headers, and it compiles again.

The main project is an MFC application, which uses stdafx.h. When do I
use it or not use it? I guess a better question would be to ask if
stdafx.h should only be used in the MFC application itself, not the static
lib?

Can you clarify this a bit for me?

Thanks!