A link to how to configure this ...

[StingyJack]

... to replace existing datacontractserializer/xml based wcf services would be good to have here.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 36986f04-8737-6bc4-d700-ff571f6b6de2
• Version Independent ID: e6d91a92-c577-954e-1405-825ce6b31ccf
• Content: DataContractJsonSerializer Class (System.Runtime.Serialization.Json)
• Content Source: xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml
• Product: dotnet-api
• GitHub Login: @dotnet-bot
• Microsoft Alias: dotnetcontent

[BillWagner]

Thanks for pointing this out @StingyJack We've added it to our backlog.

[KingdomOfEnds]

Hi @StingyJack! - A great, related, article with numerous examples (including config) is available here: https://docs.microsoft.com/dotnet/framework/wcf/feature-details/how-to-serialize-and-deserialize-json-data. If you browse on the left-hand side, you'll see several WCF and XML-related examples to review as well. I hope that provides the answer you're looking for!

[StingyJack]

Thanks @KingdomOfEnds - I've been through article too but it does not cover the topic I'm looking for. I'm looking for how to replace the default DataContractSerializer with this one by updating the client and server .config files. There are bits and pieces all over the internet, but most talk about replacing with the Newtonsoft serializer and require some code. Any ideas for where else I may find what I'm looking for?

[KingdomOfEnds]

Hi @StingyJack - I see. I dug up a few articles that I hope will more directly address the issue of configuring WCF to accept a different DataContractSerializer:

• https://docs.microsoft.com/dotnet/framework/wcf/feature-details/serialization-and-deserialization
• https://blogs.msdn.microsoft.com/carlosfigueira/2011/05/02/wcf-extensibility-message-formatters/

I agree that adding some examples to the article directly would be helpful.

[StingyJack]

Thanks again but those require changes to the code objects that will be transmitted, and while most of the ones I would be transmitting are code generated, there are many that are not and would require hand coding the attributes, That effort is why I wasn't keen on using Protobuf or other like options, as I already have [DataContract] and [DataMember] present on everything and was trying to leverage that by using the out of the box DataContractJsonSerializer (i know protobuf szn can be configged externally but that is still going to be a large config file).