Windows apps
Collapse the table of content
Expand the table of content
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

IBindCtx interface

Provides access to a bind context, which is an object that stores information about a particular moniker binding operation.

When to implement

You do not need to implement this interface. The system provides an IBindCtx implementation, accessible though a call to the CreateBindCtx function, that is suitable for all situations.

When to use

Anyone writing a new moniker class by implementing the IMoniker interface must call IBindCtx methods in the implementation of several IMoniker methods. Moniker providers (servers that hand out monikers to identify their objects) may also need to call IBindCtx methods from their implementations of the IOleItemContainer or IParseDisplayName interface.

Moniker clients (objects that use monikers to acquire interface pointers to other objects) do not typically call many IBindCtx methods. Instead, they simply pass a bind context as a parameter in a call to an IMoniker method. To acquire an interface pointer and activate the indicated object (called binding to an object), moniker clients typically do the following:

  1. Call the CreateBindCtx function to create a bind context and get a pointer to the IBindCtx interface on the bind context object.
  2. If desired (although this is rarely necessary), the moniker client can call IBindCtx::SetBindOptions to specify the bind options.
  3. Pass the bind context as a parameter to the desired IMoniker method (usually IMoniker::BindToObject).
  4. Call IUnknown::Release on the bind context to release it.

Although applications that act as link containers (container applications that allow their documents to contain linked objects) are moniker clients, they rarely call IMoniker methods directly. Generally, they manipulate linked objects through the system implementation (in the default handler) of the IOleLink interface. This implementation calls the appropriate IMoniker methods as needed and, in doing so, passes pointers to IBindCtx interfaces on the proper bind context objects.


The IBindCtx interface inherits from the IUnknown interface. IBindCtx also has these types of members:


The IBindCtx interface has these methods.


Retrieves a pointer to an interface that can be used to enumerate the keys of the bind context's string-keyed table of pointers.


Retrieves the binding options stored in this bind context.


Retrieves an interface pointer to the object associated with the specified key in the bind context's string-keyed table of pointers.


Retrieves an interface pointer to the running object table (ROT) for the computer on which this bind context is running.


Registers an object with the bind context to ensure that the object remains active until the bind context is released.


Associates an object with a string key in the bind context's string-keyed table of pointers.


Releases all pointers to all objects that were previously registered by calls to RegisterObjectBound.


Removes the object from the bind context, undoing a previous call to RegisterObjectBound.


Removes the specified key and its associated pointer from the bind context's string-keyed table of objects.


Sets new values for the binding parameters stored in the bind context.



A bind context includes the following information:

  • A BIND_OPTS structure containing a set of parameters that do not change during the binding operation. When a composite moniker is bound, each component uses the same bind context, so it acts as a mechanism for passing the same parameters to each component of a composite moniker.
  • A set of pointers to objects that the binding operation has activated. The bind context holds pointers to these bound objects, keeping them loaded and thus eliminating redundant activations if the objects are needed again during subsequent binding operations.
  • A pointer to the running object table (ROT) on the same computer as the process that started the bind operation. Moniker implementations that need to access the ROT should use the IBindCtx::GetRunningObjectTable method rather than using the GetRunningObjectTable function. This allows future enhancements to the system's IBindCtx implementation to modify binding behavior.
  • A table of interface pointers, each associated with a string key. This capability enables moniker implementations to store interface pointers under a well-known string so that they can later be retrieved from the bind context. For example, OLE defines several string keys ("ExceededDeadline", "ConnectManually", and so on) that can be used to store a pointer to the object that caused an error during a binding operation.


Minimum supported client

Windows 2000 Professional [desktop apps | UWP apps]

Minimum supported server

Windows 2000 Server [desktop apps | UWP apps]






IID_IBindCtx is defined as 0000000e-0000-0000-C000-000000000046

See also




© 2018 Microsoft