SerialPort issue transmitting Unicode characters

The managed implementation in .NET Framework 2.0 and .NET Compact Framework 2.0 supports the Encoding property that allows developers to specify the encoding they would use to transmit data over a serial port connection. The property defaults to ASCIIEncoding, which only allows ASCII characters to be transmitted. To transmit non-ASCII Unicode characters over the wire,…

1

Deadlock issue on closing SerialPort

NETCF V2’s SerialPort implementation provides four public events for developers. They can add custom event handlers to handle these events. Since these event handlers are executed by ThreadPool threads, if the developer wants to update form fields with the received data, he/she would need to invoke the associated methods on the form to ask the GUI…

1

Directory.Exists() Issue

On Windows CE 4.X based devices, Directory.Exists() treats path names ending with a slash “\” differently. As an example, Directory.Exists(“\\temp”) will return true if the “temp” directory exists. However, the following call will return false even though the directory exists: Directory.Exists(“\\temp\\”) On Windows Mobile 5.0 devices, NETCF’s behavior is consistent with Desktop’s; that is, Directory.Exists()…

0

Power Notifications and Serial Port

NETCF V2 adds the support of a managed SerialPort class to allow developers to directly access the serial ports on mobile devices, enabling communication with GPS, bar code readers, or other mobile devices within managed code. These peripherals may be sending data to the device on a continuous or intermittent basis. Thus, it is important that…

3