Re: Using MFC dll from non-MFC application

From:

"Scott McPhillips [MVP]" <org-dot-mvps-at-scottmcp>

Newsgroups:

microsoft.public.vc.mfc

Date:

Mon, 12 May 2008 23:22:02 -0400

Message-ID:

<uFCHQiKtIHA.4912@TK2MSFTNGP03.phx.gbl>

"JRGlide" <JRGlide@discussions.microsoft.com> wrote in message
news:DDB63C1D-08F9-4DCF-803B-DD7B6A2D204E@microsoft.com...

Today I tried using the CWinThread as David and Scott suggested, but I had
some problems. When I created my own CWinThread and moved my InitInstance
over from my CWinApp, I got undefines on all the Doc/View type calls, such
as:

AddDocTemplate(pDocTemplate);
ParseCommandLine(cmdInfo);
ProcessShellCommand(cmdInfo)

I think this is because they are only defined in CWinApp and not in
CWinThread.

So then I started thinking that since CWinApp is derived from CWinThread,
that maybe I could just call AfxBeginThread and pass it the original
application instead, like this:

CViewPointCloudApp *pointCloudThread = (CViewPointCloudApp*)
AfxBeginThread
(RUNTIME_CLASS (CViewPointCloudApp));

It sounds good in theory anyway, but I got undefines. The RUNTIME_CLASS
macro didn't like me passing an CWinApp instead of a CWinThread.

Did I understand you right, is this how I should be doing it?

Otherwise, my next idea is to either convert the program and get rid of
the
Doc/View and go straight to a Frame and child window (I don't really need
Doc/View anyway)...

Those CWinApp functions are not applicable (you don't have a command line or
a shell command anyway). The objective inside the thread's InitInstance
should be to create the windows. You could keep the doc/view by looking
inside the MFC source and recreating the calls it makes, or you could simply
create a frame and child window by calling their Create.

--
Scott McPhillips [VC++ MVP]