Application Connectivity (Windows CE 5.0)
Platform Manager supports application connectivity. Application connectivity is a communications framework that allows you to establish a connection between an application running on a development workstation and a target device. Remote Tools use the application connectivity support in Platform Manager to connect to a target device.
For information about connecting a remote tool to a target device, see Connecting to a Target Device with a Remote Tool.
In the IDE, a device represents the information that is required by Platform Manager to establish application connectivity with a target device. With an application on a development workstation, you can only connect successfully to a target device if you correctly configure a device for that target device. A device includes the selection of a startup server and a transport. A transport allows the target device and desktop side of Platform Manager to communicate over the communications hardware. A startup server initiates the connection by downloading the device side of Platform Manager to the target device and starting the device side of Platform Manager on the target device. For more information about startup servers and transports, see Startup Server Selection and Transport Selection.
For information about how a device, startup server, and transport fit into the object model for Platform Manager, see Platform Manager Object Model.
The application connectivity provided by Platform Manager is similar in some ways to Microsoft ActiveSync®, which is another application connectivity service. In fact, some Platform Manager startup servers and transports require an ActiveSync connection to provide application connectivity. However, Platform Manager is designed to support development tools, while ActiveSync is mostly a data-synchronization protocol.
To use a remote tool connection between an application and a target device, you must first configure your communications hardware. In some cases, this connection requires a serial connection to the target device and an ActiveSync connection from the Repllog.exe process on the target device.
The following table shows the connection configurations that require a serial connection with ActiveSync.
Transport | Startup server | Requires serial connection with ActiveSync |
---|---|---|
ActiveSync | CESH | Yes |
ActiveSync | Yes | |
Manual server | Yes | |
TCP/IP | CESH | No |
ActiveSync | Yes | |
Manual server | No | |
KITL | CESH | No |
ActiveSync | Yes | |
Manual server | No |
Note You can establish a TCP/IP connection to a target device over a serial connection. In the TCP/IP Transport Configuration dialog box, choose Configure automatically over serial. For more information, see TCP/IP Transport.
See Also
Platform Manager and the SDK | Core Kernel Connectivity
Send Feedback on this topic to the authors