ICcSvcHost (Windows CE 5.0)
This interface provides methods and properties that implement the Core Connectivity Service Host framework.
The Service Host acts as a broker component between client applications and Core Connectivity services such as the following:
- Kernel Download
- Kernel Transport
- Application Download
- Application Transport
- Custom services
The Core Connectivity Service Host is a COM server that enables the creation of services on a per-user basis.
When a client application requests a Core Connectivity service object, such as a Kernel Transport, Service Host caches a copy of the service. In addition, the Service Host manages the lifetime of the service, caching it until the client calls ICcSvcHost::Unlock.
Methods
The following tables show the methods for this interface. The interface inherits the methods for the IUnknown and IDispatch.
The following table shows the methods for the IDispatch interface.
Method | Description |
---|---|
IDispatch::GetIDsOfNames | Maps a single member name and an optional set of parameter names to a corresponding set of integer dispatch identifiers (DISPIDs).
These identifiers can then be used on subsequent calls to IDispatch::Invoke. |
IDispatch::GetTypeInfo | Retrieves the type information for an object. |
IDispatch::GetTypeInfoCount | Retrieves the number of type information interfaces provided by an object, either zero (0) or 1. |
IDispatch::Invoke | Provides access to properties and methods exposed by an object. |
The following table shows methods for the ICcSvcHost interface.
Method | Description |
---|---|
ICcSvcHost::GetService | Creates a service for a device in a given service category. |
ICcSvcHost::Version | Gets the Service Host version. |
ICcSvcHost::DisplayServices | Brings up the Target Connectivity Options Dialog Box dialog box. |
ICcSvcHost::GetDeviceState | Returns the current state of the device.
Supported values are in use, or not in use. |
Requirements
OS Version: Windows CE 5.0 and later.
Header: CcSvcHost.h.
Link Library: none.
See Also
Send Feedback on this topic to the authors