Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Brian Muth (bmuthSWI.COM)
Date: Thu Aug 09 2001 - 00:47:40 CDT
> On the other hand I strongly feel that the facts should be stated in
> unambiguous terms (to newbie or scholar, not withstanding). When one
> remotely creates a COM object, it depends which interfaces u want to
> use. U don't have to use very interface. And this is what the original
> sender of the mail, Chuck Ricketts, should know.
> And the statement " This is simply another matter if that component is
> implemented in such a way so as to assume certain functionalities from
> its creator (container)." is certainly not meaningless. Read it again.
I've read it several times, and it still is pretty cloudy.
For the benefit of newbies and scholars alike, let me (cough, cough ...
slow drumroll) try to be lucid.
When I hear the term "embeddable ActiveX control", I equate that to
ATL's "Full Control" or VB6's "ActiveX Control". This type of COM object
typically implements interfaces such as IOleControl, IOleObject,
IDataObject, IViewObject, and others that provide the necessary
handshaking that permits the control to display itself within a
displayable region within the host. These COM components are NOT
remoteable. Period. Specifically, IViewObject cannot be marshaled.
On the other hand, the more general term "COM object" simply implies as
a minimum, the implementation of IUnknown. This the equivalent of ATL's
"Simple Object", or VB6's class module. These COM objects are often
remotable, but is dependent on the author's intention. (Is this what you
Granted, there are situations where you can instantiate a full ActiveX
control on a remote machine, forego the GUI handshaking, and then call
one specific interface that CAN be marshaled to perform a specific
function. But Chuck used the phrase "where each object is a VB form
embeddable ActiveX control", and I don't believe this was what he meant.
I suspect this is what you were trying to get at.
Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
contains important info. Save time, search the archives at
To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM