|
CoRegisterClassObject
Registers an EXE class object with OLE so that other applications can connect
to it. EXE object applications should call CoRegisterClassObject on startup. It can also be used to register internal objects for use by the
same EXE or other code (such as DLLs) that the EXE uses.
STDAPI CoRegisterClassObject(
REFCLSID rclsid,
| //Class identifier to be registered
| IUnknown * pUnk,
| //Pointer to the class object
| DWORD dwClsContext,
| //Context for running executable code
| DWORD flags,
| //How to connect to the class object
| LPDWORD * lpdwRegister
| //Pointer to the value returned
| );
|
|
Parameters
rclsid
Specifies the CLSID registered.
pUnk
Points to the class object whose availability is being published.
dwClsContext
Specifies the context in which the executable code is to be run. For
information on these context values, see the CLSCTX enumeration.
flags
Determines how connections are made to the class object. For information on
these flags, see the REGCLS enumeration.
lpdwRegister
Points to the value returned by CoRegisterClassObject that identifies the class object; later used by the CoRevokeClassObject function to revoke the registration.
Return Values
S_OK
Indicates the class object was registered successfully.
CO_E_OBJISREG
Indicates already registered in the class object table.
E_OUTOFMEMORY
Out of memory.
E_INVALIDARG
Indicates one or more arguments are invalid.
E_UNEXPECTED
Indicates an unexpected error occurred.
Comments
Only EXE object applications call CoRegisterClassObject. Servers that can create and support more than one kind of object (such as
multiple types of embeddable objects) must also register each of class of object
it supports. Object handlers or DLL object applications do not call this
function; instead, they must implement and export the DllGetClassObject function.
When a multiple-use EXE object application is started, it must create a class
object with the IClassFactory interface on it and register it with a call to CoRegisterClassObject. Object applications that support several different object definitions must
allocate a different class object for each.
Multiple registrations of the same class object are independent and do not
produce an error. Each subsequent registration yields a unique key in lpdwRegister.
Multiple document interface (MDI) applications must register their class
objects. Single document interface (SDI) applications must register their class
objects only if they can be started by means of the /Embedding switch.
The server for a class object should call CoRevokeClassObject to revoke the class object when all of the following are true:
- There are no existing instances of the object definition
- There are no locks on the class object
- The application providing services to the class object is not under user
control (not visible to the user on the display).
After the class object is revoked, when its reference count reaches zero, the
class object can be destroyed, allowing the application to exit.
For information on the flags parameter, refer to the REGCLS enumeration.
See Also
CoGetClassObject, CoRevokeClassObject, DllGetClassObject, REGCLS, CLSCTX
Related LinksSoftware for Delphi and C++ Builder developers
Software for Visual Studio .NET developers
Software for Visual Basic 6 developers
Delphi Tips&Tricks
MegaDetailed.NET
TMS Scripter Studio Pro components for Delphi/C++Builder
More Online Helps Win32 Programmer's Reference (win32.hlp)
Win32 Multimedia Programmer's Reference (mmedia.hlp)
Microsoft Windows Pen API Programmer's Reference (penapi.hlp)
Microsoft Windows Sockets 2 Reference (sock2.hlp)
Microsoft Windows Telephony API (TAPI) Programmer's Reference (sock2.hlp)
Unix Manual Pages
|
