An automation server cannot pass a pointer to the picture object's IPictureDisp implementation across process boundaries

This article was previously published under Q150034
This article has been archived. It is offered "as is" and will no longer be updated.
An automation server that implements a Picture object wrapped by the CPictureHolder class in MFC fails when it attempts to pass a pointer to the picture object's IPictureDisp implementation across process boundaries.
IPictureDisp gains access to methods of the Picture object that cannot be marshaled across process boundaries. For example, IPictureDisp supports DISPID_PICT_RENDER to gain access to the Render method of the Picture object. The Render method takes a handle to a device context as the first parameter. Device context handles cannot be marshaled.

Dispatch interfaces can normally be marshalled by using the IDispatch marshaling code, but the Picture object implements IMarshal specifically to cause its marshaling to fail.
This behavior is by design.
The ClassWizard in Visual C++ allows you to select a return type of LPPICTUREDISP for a method. This method might return the IPictureDisp interface obtained by calling CPictureHolder::GetPictureDispatch. However, if this method is called by a controller running in another process, the method fails and returns an error code of E_FAIL.

Because the Picture object causes the marshaling of IPictureDisp to fail, problems can also occur when trying to obtain an IPictureDisp interface across thread boundaries in a multiple-thread apartment model object.
For more information on marshaling, please see "Inside OLE," second edition, by Kraig Brockschmidt, Chapter 6, "Local/Remote Transparency," published by Microsoft Press.

Article ID: 150034 - Last Review: 02/28/2014 08:02:33 - Revision: 3.1

Microsoft Foundation Class Library 4.2

  • kbnosurvey kbarchive kbtshoot kbbitmap kbautomation kbprb kbctrl KB150034