Using Custom OCX Controls
This section covers how you can add functionality to your snap-in that enables it to launch a custom OCX control.
A snap-in can launch an OCX control in the result pane of an MMC console. The OCX control runs in the same thread as the snap-in, so snap-in developers only need to deal with threading issues if their OCX controls are multithreaded.
Be aware that custom OCX controls should be used sparingly, because they cannot be extended by other snap-ins. Additionally, MMC will not send Cut, Copy, Paste, or Rename notifications to OCX controls. Snap-ins should instead use list views where possible.
The MMC SDK specifies two interface methods and a number of other constructs for working with custom OCX controls. MMC calls the snap-in's implementation of IComponent::GetResultViewType to display the result pane for a particular scope item. The snap-in uses the method to indicate to MMC that an OCX view should be launched and provides MMC with the CLSID of the OCX control. The snap-in can also specify whether a single instance of the OCX control should be cached and reused each time the scope item is selected, or whether MMC should instead destroy the cached OCX control and create a new custom control each time the item is selected. This is done using the MMC_VIEW_OPTIONS_CREATENEW option.
The second method, IConsole2::QueryResultView, can be used to query for the OCX control's IUnknown interface pointer. The snap-in can also acquire this pointer in a number of other ways, for example while handling the MMCN_INITOCX notification message.
MMC sends the snap-in an MMCN_INITOCX notification message with an interface pointer to the custom OCX control's IUnknown interface. The snap-in can use the pointer to perform any initialization of the OCX control before it is displayed in the result pane.
MMC sends the snap-in an MMCN_SHOW notification upon deselection of the result pane with the OCX view. The arg parameter of the notification is set to FALSE, indicating that the OCX view is going out of focus. At this time, the snap-in can do any necessary clean-up, such as ensuring that the OCX control is properly destroyed.