The following table shows the return values for this method.

A bind context maintains a table of interface pointers, each associated with a string key. This enables communication between a moniker implementation and the caller that initiated the binding operation. One party can store an interface pointer under a string known to both parties so that the other party can later retrieve it from the bind context.

Binding operations subsequent to the use of this method can use the IBindCtx::GetObjectParammethod to retrieve the stored pointer.

To determine whether the platform supports this interface, see Determining Supported COM APIs.

Notes to Callers

IBindCtx::RegisterObjectParamis useful to those implementing a new moniker class (through an implementation of IMoniker) and to moniker clients (those who use monikers to bind to objects).

In implementing a new moniker class, you call this method when an error occurs during moniker binding to inform the caller of the cause of the error. The key that you would obtain with a call to this method depends on the error condition. Following is a list of common moniker binding errors, each describing the keys that would be appropriate:

• MK_E_EXCEEDEDDEADLINE. If a binding operation exceeds its deadline because a given object is not running, you should register the object's moniker using the first unused key from the list: ExceededDeadline, ExceededDeadline1, ExceededDeadline2, and so on.
  
  If the caller later finds the moniker in the Running Object Table, the caller can retry the binding operation.
  
  
• MK_E_CONNECTMANUALLY. The ConnectManually key indicates a moniker whose binding requires assistance from the end user.
  
  To request that the user manually connect to the object, the caller can retry the binding operation after showing the moniker's display name. Common reasons for this error are that a password is needed or that a floppy needs to be mounted.
  
  
• E_CLASSNOTFOUND. The ClassNotFound key indicates a moniker whose class could not be found. (The server for the object identified by this moniker could not be located.)
  
  If this key is used for an OLE compound-document object, the caller can use the IMoniker::BindToStoragemethod to bind to the object and then try to carry out a Treat As... or Convert To... operation to associate the object with a different server. If this is successful, the caller can retry the binding operation.
  
  

If you are a moniker client with detailed knowledge of the implementation of the moniker you are using, you can also call this method to pass private information to that implementation.

You can define new strings as keys for storing pointers. By convention, you should use key names that begin with the string form of the CLSID of the moniker class. (See the StringFromCLSIDfunction.)

If the pszKeyparameter matches the name of an existing key in the bind context's table, the new object replaces the existing object in the table.

When you register an object using this method, the object is not released until one of the following occurs:

• It is replaced in the table by another object with the same key.
  
  
• It is removed from the table by a call to the IBindCtx::RevokeObjectParammethod.
  
  
• The bind context is released. All registered objects are released when the bind context is released.