D
David Ching
Ajay said:This is a MFC related issue and would be present even if all DLLs are
compatible(whatever that means) or not. An MFC extension DLL shouldnt
be used to write a plugin/addin to a non-MFC app. On the other hand, a
MFC regular DLL will work fine as a plugin in a Office app. OP's issue
is not about accessing the object model but rather co-existing in it
in a particular way.
Yes, a MFC Regular DLL could most certainly work as an Outlook plug-in. At
first, I thought Dmitry raises an interesting point that the plug-in, MFC or
not, that links with MSVCRT dynamically can potentially conflict with
another plug-in or Outlook.exe itself that might link with another version
of the runtime. Since there can be only one runtime in the Outlook process,
it has to be the same. Since there is no guarantee what version of
MSVCRT.DLL Outlook itself (or another plug-in) may be using, the correct
thing is to make a MFC Regular DLL that is statically linked.
However, I think XP and later solve this problem by allowing multiple
versions of the runtime (or any other) DLL's to load side-by-side. So even
this is not a problem. An MFC Regular DLL either statically or dynamically
linked would seem to work.
-- David