Re: Why Domodal Crashing?

From:

"Leo Violette" <nineballer@comcast.net>

Newsgroups:

microsoft.public.vc.mfc,microsoft.public.office.developer.com.add_ins

Date:

Mon, 2 Mar 2009 12:42:57 -0800

Message-ID:

<2640E812-F56E-4179-9A81-C171E939AE1A@microsoft.com>

Try this...

// You're regular DLL that uses MFC (as opposed to an MFC Extension DLL),
should have a function
// like this to show your dialog.
INT_PTR DLLFuncShowMyDialog(void)
{
    // Setup the MFC state for the current thread.
    AFX_MANAGE_STATE(AfxGetStaticModuleState());
    CMyDialog Dlg;
    INT_PTR iRC = Dlg.DoModal();
    return iRC;
}

"RLN" <RLN@discussions.microsoft.com> wrote in message
news:E960B611-4754-43AD-A4AF-80821D73DD7A@microsoft.com...

ok fine. Now I freshly Created the ATL COM DLL Project and intergrated
office
addin.
It will create 1 Toolbar button in office . On clicking the button
displaying the messagebox. Working fine. no issues.
After That I just created 1 Dialog and added a MFC class for that. No
Additional code.
Just
AfxSetResourceHandle()
CMyDialog Dlg;
Dlg.DModal();
//reset the resource handle.

That's all . Dialog box residing the same add-in dll. Now No mfc extension
dll or mfc regular dll just ATL COM dll. Now also crashing on the same
location
if (!AfxGetThread()->PumpMessage())

Then wat is the problem now.
--
WM_QUIT
RLN

--
WM_QUIT
RLN

"David Ching" wrote:

"Dmitry Streblechenko" <dmitry@dimastr.com> wrote in message
news:ufnud7WmJHA.5028@TK2MSFTNGP04.phx.gbl...

Why would it matter what it is written in? Windows that live in
different
dlls communicate using Windows API only.
It makes no difference wahtsoever whether the window was created using
MFC, ATL or some other lanagugae (e.g. Delphi or VB).

An MFC Extension DLL can export classes derived from MFC classes, so it
is
not true that communication with this DLL is through the Windows API
only.
And even if in this case the exported functions did not use MFC classes,
the
requirements of the exported functions are different. For example,
exports
in an MFC Extension DLL do not have to call AFX_MANAGE_STATE(), but they
do
from an MFC Regular DLL (thanks Ajay). It does sound like an MFC state
issue due to the fact that DoModal() is crashing... the dialog resource
is
probably not being found.

-- David