CLSCTX_INPROC_SERVER

The code that creates and manages objects of this class runs in the same process as the caller of the function specifying the class context.

CLSCTX_INPROC_HANDLER

The code that manages objects of this class is an in-process handler. This is a dynamic-link library (DLL) that runs in the client process and implements client-side structures of this class when instances of the class are accessed remotely.

CLSCTX_LOCAL_SERVER

The EXE code that creates and manages objects of this class is loaded in a separate process space, which runs on same machine but in a different process.

CLSCTX_REMOTE_SERVER

A remote machine context. The LocalServer32 or LocalService code that creates and manages objects of this class is run on a different machine.

CLSCTX_SERVER

Indicates server code, whether in-process, local, or remote.

This definition ORs CLSCTX_INPROC_SERVER, CLSCTX_LOCAL_SERVER, and CLSCTX_REMOTE_SERVER.

CLSCTX_ALL

Indicates all class contexts. This definition ORs CLSCTX_INPROC_HANDLER and CLSCTX_SERVER.

Values from the CLSCTXenumeration are used in activation calls (such as CoCreateInstance, CoCreateInstanceEx, and CoGetClassObject) to indicate the preferred execution contexts (in-process, local, or remote) in which an object is to be run.

They are also used in calls to CoRegisterClassObjectto indicate the set of execution contexts in which a class object is to be made available for requests to construct instances ( IClassFactory::CreateInstance).

To indicate that more than one context is acceptable, you can string multiple values together with Boolean ORs. The contexts are tried in the order in which they are listed.

The following table shows how other OLE functions and methods that call CoGetClassObjectuse the CLSCTXvalues.

The CLSCTX_REMOTE_SERVER value is added to the CLSCTXenumeration for the distributed Component Object Model (COM). The CLSCTX_SERVER and CLSCTX_ALL constants are further updated to include the CLSCTX_REMOTE_SERVER value.

Given a set of CLSCTXflags, dwClsCtx, the execution context to be used depends on the availability of registered class codes and other parameters according to the following algorithm.

The first part of the processing determines whether CLSCTX_REMOTE SERVER should be specified as follows.

If the call specifies an explicit COSERVERINFOstructure indicating a machine different from the current machine, or if there is no explicit COSERVERINFOstructure specified, but the specified class is registered with either the RemoteServerNameor ActivateAtStoragenamed value, CLSCTX_REMOTE_SERVER is implied and is added to dwClsCtx.

The second case allows applications written prior to the release of distributed COM to be the configuration of classes for remote activation to be used by client applications available prior to DCOM and the CLSCTX_REMOTE_SERVER flag.

The cases in which there would be no explicit COSERVERINFOstructure are (1) the value is specified as NULL and (2) it is not one of the function parameters, as would be the case in calls to CoCreateInstanceor CoGetClassObjectin existing applications.

If the explicit COSERVERINFOparameter indicates the current computer, CLSCTX_REMOTE_SERVER is removed (if present) from dwClsCtx.

The rest of the processing proceeds by looking at the values of dwClsCtxin the following sequence.

1. If dwClsCtxincludes CLSCTX_REMOTE_SERVER and no COSERVERINFOparameter is specified, and the activation request indicates a persistent state from which to initialize the object (with CoGetInstanceFromFileor CoGetInstanceFromIStorageor, for a file moniker, in a call to IMoniker::BindToObject), and the class has an ActivateAtStoragesubkey or no class registry information whatsoever, the request to activate and initialize is forwarded to the computer where the persistent state resides.
   
   
2. If dwClsCtx includes CLSCTX_INPROC_SERVER, the class code in the DLL found under the class's InprocServer32 key is used if this key exists. The class code will run within the same process as the caller.
   
   
3. If dwClsCtx includes CLSCTX_INPROC_HANDLER, the class code in the DLL found under the class's InprocHandler32 key is used if this key exists. The class code will run within the same process as the caller.
   
   
4. If dwClsCtx includes CLSCTX_LOCAL_SERVER, the class code in the Microsoft® Win32® service found under the class's LocalService key is used if this key exists.
   
   If no Win32 service is specified, but an EXE is specified under that same key, the class code associated with that EXE is used. The class code (in either case) will be run in a separate service process on the same machine as the caller.
   
   
5. If dwClsCtx is set to CLSCTX_REMOTE_SERVER and an additional COSERVERINFO parameter to the function specifies a particular remote machine, a request to activate is forwarded to this remote machine with dwClsCtx modified to be CLSCTX_LOCAL_SERVER.
   
   The class code will run in its own process on this specific machine, which must be different from that of the caller.
   
   
6. If dwClsCtx includes CLSCTX_REMOTE_SERVER and no COSERVERINFO parameter is specified and a computer name is given under the class's RemoteServerName named value, the request to activate is forwarded to this remote computer with dwClsCtx modified to be CLSCTX_LOCAL_SERVER.
   
   The class code will run in its own process on this specific computer, which must be different from that of the caller.
   
   

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