Re: CObject use?

From:

David Wilkinson <no-reply@effisols.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Sun, 10 Jun 2007 06:45:44 -0500

Message-ID:

<e3RB#x0qHHA.1204@TK2MSFTNGP04.phx.gbl>

Bryan wrote:

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?

Bryan:

stdafx.h is not an MFC header; it is the "pre-compiled header" file.
Each project should have its own stdafx.h (or it need not have one if it
is not using pre-compiled headers). Any kind of project can have an
stdafx.h file, not just MFC projects. Normally, in an MFC project, the
stdafx.h file will contain the necessary includes for using MFC.

What you say about your static lib does not make much sense to me. If
this static library needs MFC, then you should not remove its stdafx.h.
Also, stdafx.h is not normally included in header files; rather it is
included as the first include in each implementation file (a bad design,
perhaps, but that is how pre-compiled headers are always done in VC)..

--
David Wilkinson
Visual C++ MVP