Scott,
Yes, you could write either (1) an XPCOM component that hosts one or
more
MSCOM components or (2) write an MSCOM component that hosts one or more
XPCOM components or (3) write an application that can play host to both
MSCOM and XPCOM components.
I would avoid attempting to write code that treated IUnknown pointers
and
nsISupports pointers as interchangeable. Also, you may need to play some
namespace games in C++ to avoid name collisions.
However, most of the fun of MSCOM and XPCOM comes from scripting and
the two scripting interfaces are definitely not interchangeable. The
VBScript and JScript script engines would not be able to use XPConnect
to access scriptable XPCOM components and likewise XPConnect would not
be able to allow Javascript to manipulate MSCOM components
out-of-the-box.
Personally, I would be more inclined to pick one or the other based upon
what was needed (ie. is supporting MSCOM a requirement or is
cross-platform compatibility a requirement?) instead of trying to do
both at the same time.
-rick
Scott Velez wrote:
> Is there any way for XPCOM to call into a Windows specific IDispatch
> based COM component?
>
> Scott
