Connection Method Selection

During development, you must have a fast and reliable connection between the smart device and the development computer. Although the smart device emulators can be used in most stages of development, testing your application on a real-world piece of hardware is an important part of the development cycle.

The most common connection options are as follows:

  • Connecting to the Device Emulator by using the DMA transport.

    This transport eliminates network-related connection issues and typically ships as the default transport. Unless you have some serious reason to use another transport, always use the DMA transport for the Device Emulator.

  • Connecting to a physical device by using ActiveSync 4.x or Windows Mobile Device Center and a USB port.

You can access these and other options from the Visual Studio Tools menu. For more information, see How to: Set Connection Options (Devices).

Note

Windows Mobile Device Center (WMDC) replaces ActiveSync in Windows Vista. Windows Vista users must install WMDC instead of ActiveSync.

ActiveSync 4.x

ActiveSync 4.x provides a connection between the development computer and a device by using cable, cradle, Bluetooth, or infrared connections. It also provides the vehicle by which required core connectivity connection and security files are automatically downloaded to the device. When you cradle a device, ActiveSync turns off all other network cards. You know your device is communicating only with the development computer. ActiveSync is the standard connection mechanism while you develop your device application.

If ActiveSync support is not available for your device, see How to: Connect to Windows CE Device Without ActiveSync.

Connection Options

Pocket PCs, Smartphones, and other Windows CE-based hardware offer many ways of linking a device and a computer. In this section, the various connection options and their advantages and disadvantages are discussed.

One or more of the following connection methods can be used depending on the hardware device involved.

  • USB Connection
    The simplest form of connection, all Pocket PC and Smartphone devices support a USB connection. Although not as fast as an Ethernet or Wireless 802.11b/g connection, the simplicity of the USB connection makes it an attractive option. Many devices are also powered by using the USB port, which is an added convenience.

  • Wired Ethernet network
    By default, Pocket PC and Smartphone devices do not support Ethernet connections without additional hardware. However, the extra speed of this connection standard makes it the preferred way to perform debugging and other data-intensive operations.

  • Wireless 802.11b/g network
    Wireless network cards are available for Pocket PCs, and several models now come with wireless networking as an integral feature. Wireless networking is as fast as a wired Ethernet network connection.

  • Bluetooth
    Many Pocket PC and Smartphone devices feature Bluetooth wireless networking. Once paired, the smart device can connect over ActiveSync as long as it is within range of the desktop computer. Because Bluetooth is not as fast as 802.11b/g wireless, avoid using it for debugging.

  • Serial connection
    If no USB or wired or wireless networking options are available, a serial port makes an acceptable, if slow, way to connect a smart device to a development computer.

  • Infrared connection
    Infrared connections require no additional wiring, and both Pocket PC and Smartphone devices come with IrDA ports as standard. However, infrared connections require line-of-sight to operate reliably, and even then performance is not acceptable for debugging. However, IrDA can be useful as a last resort technique to copy files to devices.

See Also

Tasks

Connectivity Troubleshooting (Devices)

Other Resources

Working with Smart Devices and Emulators