Date Added: Nov 2007
One seemingly strange behavior that Windows CE devices (including Pocket PC, Smartphone and Windows Mobile devices) exhibit is that when the query the device time, the get back either a zero of some constant but invalid value for the milliseconds field. This is true whether the call GetLocalTime or GetSystemTime in native code or DateTime. Now in managed code. Why is it that devices running an OS that has real-time capabilities can't provide the as developers with a clock that has simple millisecond resolution? The answer lies not in the OS - which is quite capable of giving that resolution - but in how the time function is implemented by the device OEM.