Or you might consider switching to a different JSON serializer, such as, where you can control whether to ignore or respect. You might also consider generating contract-appropriate classes with SvcUtil.exe then using automapper to map your old classes to your new classes. (Remember, these are ignored by XmlSerializer so you're pre-existing XML schema will be unchanged.) This should be harmless unless you're using BinaryFormatter somewhere you probably are not.Īdd and attributes to the generated classes. Thus you're going to do some sort of manual fix: Unfortunately, I don't see any xsd command line switches to disable this attribute. Similarly the data contract serializers all ignore XmlSerializer control attributes.) (It also completely ignores data contract attributes.

XmlSerializer completely ignores this attribute since it can only serialize public members. What is a bit odd is that xsd.exe doesn't need to add to its generated classes. When this serializer goes to generate a default, implicit data contract for a type without data contract attributes, it notices the attribute and respects it, generating a contract to serialize and deserialize public and private fields.

Under the covers, WCF uses DataContractJsonSerializer to serialize to and from JSON. When this attribute is applied to a type, it signifies that instances of the type can be serialized by serializing all private and public fields - not the properties. The reason you are seeing private fields rather than public properties in your JSON is that xsd.exe has marked your classes with. Return (messageVersion, parameters, result) If (headers != null & headers.Contains('application/json')) (Which is the default type anyway) var headers = requestProperty.Headers ? requestProperty.Headers

That is the code where it fails, JsonDispatchMessageFormatter is of the type MultiplexingDispatchMessageFormatter. Is there any solution to this where I do not need to use the SvcUtil.exe, because therefore I would need to change my schema. The problem is, what I found out so far, that xsd.exe does not generate DataContract and DataMember Attributes.

Everthing works fine as long as I request XML, but it fails if I want JSON as response. I have a XML schema from which I generated my classes by using xsd.exe. I want to write a RESTful Webservice with WCF which is able to reply in JSON and XML.

Xml xsd.exe