Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The programming model for writing services and writing device drivers is very similar in Windows CE. You can develop a server that runs on Device.exe rather than on Services.exe, but has the identical code, provided your server does not require advanced features offered by Services.exe. However developing a server that runs on Device.exe instead of on Services.exe is done at the expense of the increased stability that Services.exe offers. If a driver does not need access to hardware or it does not need to use intra-process communication to another device driver, writing it as a service for Services.exe is highly recommended.
Services.exe can also be configured to wait on connections from multiple sockets for multiple services. Upon arrival of a connection request from a particular socket, Services.exe dispatches the request to the registered service.
Note Services.exe helps prevent a device failure resulting from a service crash, but it does not prevent a resulting crash in another unrelated service. All services should be properly debugged prior to deployment.
In This Section
Activating a Service Programmatically
Registering a Service Programmatically
Configuring Services.exe to Load a Standalone Service
Using Services.exe from the Command Line
Related Sections
Services.exe OS Design Development
Send Feedback on this topic to the authors