Thanks to KbAlertz, I just received information on a known .NET CF deficiency with Typed DataSets as parameters in Web Service calls. This is not a new issue and the workarounds are not new either; however, someone just asked me this last week so I had to forward on.
Problem: In Microsoft Visual Studio .NET 2003, when you build a .NET Compact Framework project that uses an XML Web service that exposes a typed DataSet as a WebMethod, several compiler errors occur.
Cause: The errors occur because Visual Studio .NET inserts many serialization attributes in the proxy file that the .NET Compact Framework does not support.
The workarounds for this are not painful. One solution is to change the Web Service method so that is doesn't pass Typed DataSets, which is not a great solution if other .NET platforms are using the same method. The other alternative is to change the proxy on the device by commenting out the serialization attributes. The resulting issue here is that regeneration of the proxy will require the commenting out of the serialization attributes.
I have mixed feelings about passing DataSets to devices anyway due to performance issues. But that will be improved over time (faster .NET CF, bigger "badder" devices, etc).
See Q811588 for all of the details on this issue. And make sure you subscribe to KbAlertz, the free KB notification service from Dave Wanta.
11:18:24 AM 
|
