datacontract

I understand that we can have more controls on a class if we use datacontract, however, consider the following 2 cases [DataContract] public class Customer { [DataMember] public string CustomerName {get; set;} [DataMember] public int Age{get; set;} } and public class Customer { public string CustomerName {get; set;} public int Age{get; set;} } They both get serialized correctly on .net client. And personally I do not use second example. Can anybody point me the differences in the 2 classes? I meant to send all public properties in both classes. The second version is the POCO (plain old CLR

I have scoured the Net for info on this, but most of the results are about creating WCF services or situations where the service is under your control. I am building a WCF client proxy for a RESTful JSON service which is out of my control. I am using the basic ServiceContract/DataContract pattern, and trying to let the framework do as much of the work as possible. Mostly this is working fine, but all the datetime fields coming from this external service are in a particular format, e.g. {"SomeObject": {"details":"blue and round", "lastmodified":"2013/01/02 23:14:55 +0000"} } So I get an error:

During applying data I use notifyChange with an Uri . Let's say I notify content://com.package.my/items . I have also detail Activity that displays data from content://com.package.my/items/1 . Does notifying 'general' Uri results also in 'detail' Uri being notified? thaussma The method notifyChange sends a notification for the detailed URI. But if you register a ContentObserver at ContentResolver.registerContentObserver(Uri uri, boolean notifyForDescendents, ContentObserver observer) you can register a base Uri to be notified if any descendant Uri has been changed (is used to send change

What does it mean to put a DataMemberAttribute on an interface member? How does this affect derived classes? As shown in the following signature, the DataMember attribute is not inheritable [AttributeUsageAttribute(AttributeTargets.Property|AttributeTargets.Field, Inherited = false, AllowMultiple = false)] public sealed class DataMemberAttribute : Attribute Therefore, it makes very little sense to decorate interface members with this attribute as you will have to decorate the implementing classes' members with this attribute too. In my case, I use this attributes with my WCF services. When I

I have the following type which I use as a message contract in WCF: [MessageContract(IsWrapped = true, WrapperNamespace = "http://example.com/services", WrapperName = "EchoRequest")] public class EchoRequest { public EchoRequest() { } public EchoRequest(String value) { Value = value; } [MessageBodyMember(Name = "Value", Namespace = "http://example.com/services", Order = 0)] public String Value { get; set; } } When I generate a proxy to this type using svcutil.exe , I get a client which is able to communicate to a service which hosts it, with the XML namespaces on the elements correct according

I use the DataContractJsonSerializer to parse a json string into a object hierarchie. The json string looks like this: { "groups": [ { "attributes": [ { "sortOrder": "1", "value": "A" }, { "sortOrder": "2", "value": "B" } ] }, { "attributes": { "sortOrder": "1", "value": "C" } } ] } As you can see the sub value of "attributes" can be an array or a single item. I found the code part where the problem occures: [DataContract] public class ItemGroup { [DataMember(Name="attributes")] public List<DetailItem> Items { get; set; } } This works for the first one but fails on the second one. Has anyone