A lot of questions on the MSDN forums center around how to customize a device or an app to prefer a specific network connection over another. The correct way to accomplish this is by "provisioning" the device. In fact a great many aspects of the device and the applications on it can be configured through 'provisioning' the device.&
A bug was discovered recently in the .NET Compact Framework version 2.0 (SP2 and earlier) and 3.5 that causes HttpWebRequest's directed at some HTTPS servers to fail with this error: (for web services) System.Net.WebException: Unable to read data from the transport connection. ---> System.Net.Sockets.SocketException: Unknown error (0x0).
So I had the opportunity to try out the iPhone for a day. Overall I was impressed, but there were some very basic features missing from many of the otherwise killer apps that I would greatly miss if I was to use the iPhone as my primary PDA and phone. Here is a brief summary:Then of course there's the closed platform problem, and I
The XmlSerializer in NetCF 2.0 has a bug where if a single serialization requires reflecting into types that use a mixture of Collection<T>-like types for the same T the XmlSerializer will throw an exception. Here an example where CF 2.0 would crash: This type would fail to serialize under NetCF 2.0 because T = string would a