Hello Dean, By default the simulator use "Don't link" while device builds use "Link SDK" and both should work for your own serializable types.
However if you changed this to "Link all" then it's possible that the linker will remove unused members of the Response class. You can mark them with a [Preserve] attribute (and continue linking everything), use --linkskip on the assembly that defines this type, or go back to use "Link SDK". Sebastien On Wed, Apr 4, 2012 at 2:05 PM, Dean Cleaver <[email protected]> wrote: > I’ve got a major problem I can’t work out. I have a simple class returned > from my web services: > > > > [Serializable] > > public class Response > > { > > public Response() > > { > > } > > > > public ResponseCode Code { get; set; } > > public string Data { get; set; } > > public string Description { get; set; } > > } > > > > In the simulator, it returns my “Data” correctly, but on the devices it’s > suddenly stopped, and Data is now null (can’t test all instances because I > can’t log in any more because Data is null). This appears to have only > happened in the last few hours, as I could log in this morning. > > > > As I said, simulator works fine, and a breakpoint in my server shows that it > is returning the correct Data to the devices, but it never gets there. Data > is always null on the devices now. > > > > Any ideas where to even start? > > > > Dino > > > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch > _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
