{"id":1069,"date":"2021-11-12T18:07:06","date_gmt":"2021-11-12T05:07:06","guid":{"rendered":"https:\/\/blog.wiseowls.co.nz\/?p=1069"},"modified":"2026-03-08T00:48:42","modified_gmt":"2026-03-07T11:48:42","slug":"asp-net-xml-serialisation-issues-observations-on-datacontractserializer","status":"publish","type":"post","link":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/","title":{"rendered":"ASP.NET XML serialisation issues: observations on DataContractSerializer"},"content":{"rendered":"<p>A client reached out to us with a weird problem. Their ASP.NET WebAPI project (somewhat legacy tech) needed to communicate with an application running on a mainframe (dinosaur-grade legacy tech).  But they were having XML serialisation issues&#8230;<\/p>\n<p>They had a test XML payload, but only half of that kept coming across the wire:<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"756\" height=\"528\" src=\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/11\/image.png\" alt=\"XML serialisation output showing missing fields from DataContractSerializer\" class=\"wp-image-1108\" srcset=\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/11\/image.png 756w, https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/11\/image-300x210.png 300w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px\" \/><figcaption>broken serialisation &#8211; missing fields<\/figcaption><\/figure>\n<p>first thing we suspected was missing <code>DataContract<\/code>\/<code>DataMember<\/code> attributes, but everything seemed to be okay:<\/p>\n<pre class=\"wp-block-code\"><code lang=\"csharp\" class=\"language-csharp\">[DataContract(Name = \"ComplexObject\", Namespace = \"\")]\npublic class ComplexObject\n{\n    [DataMember]\n    public int Id { get; set; }\n    [DataMember]\n    public string Name { get; set; }\n    [DataMember]\n    public string Location { get; set; }\n    [DataMember]\n    public string Reference { get; set; }\n    [DataMember]\n    public double Rate { get; set; }\n    [DataMember]\n    public double DiscountedRate { get; set; }\n}<\/code><\/pre>\n<p>After scratching our heads for a little while and trying different solution from across the entirety of StackOverflow, we managed to dig up a <a href=\"https:\/\/docs.microsoft.com\/en-us\/dotnet\/framework\/wcf\/feature-details\/data-member-order\">piece of documentation<\/a> that explained this behaviour:<\/p>\n<ol class=\"wp-block-list\">\n<li>Data members of base classes (assuming serialiser will apply these rules upwards recursively);<\/li>\n<li>Data members in alphabetical order <strong>(bingo!)<\/strong>;<\/li>\n<li>Data members specifically numbered in decorating attribute;<\/li>\n<\/ol>\n<p>With the above in mind, we got the following payload to serialise successfully:<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"762\" height=\"426\" src=\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/11\/image-1.png\" alt=\"Corrected XML output with all fields properly serialised after fixing member order\" class=\"wp-image-1109\" srcset=\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/11\/image-1.png 762w, https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/11\/image-1-300x168.png 300w\" sizes=\"auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px\" \/><figcaption>successful serialisation<\/figcaption><\/figure>\n<h2 class=\"wp-block-heading\">There are other options<\/h2>\n<p>.NET comes with at least two XML serialisers: <a href=\"https:\/\/docs.microsoft.com\/en-us\/dotnet\/api\/system.xml.serialization.xmlserializer?view=netframework-1.1\">XmlSerializer<\/a> and <a href=\"https:\/\/docs.microsoft.com\/en-us\/dotnet\/api\/system.runtime.serialization.datacontractserializer?view=netframework-3.0\">DataContractSerializer<\/a>. A lot has been written about the two. We find this <a href=\"http:\/\/www.danrigsby.com\/blog\/index.php\/2008\/03\/07\/xmlserializer-vs-datacontractserializer-serialization-in-wcf\/\">article written by Dan Rigsby<\/a> to probably be the best source of information on the topic.<\/p>\n<p>Key difference for us was the fact that <code>XmlSerializer<\/code> does not require any decorations and works out of the box. While <code>DataContractSerializer<\/code> needs us to make code changes. In our project everything was already set up with <code>DataContract<\/code>, so we did not have to change anything.<\/p>\n<p>By default, WebAPI projects come configured to leverage <code>DataContractSerializer<\/code>. It however pays to know that in case of any issues we can switch to use <code>XMLSerializer<\/code>:<\/p>\n<pre class=\"wp-block-code\"><code class=\"\">public static class WebApiConfig\n{\n    public static void Register(HttpConfiguration config)\n    {\n        config.Formatters.XmlFormatter.UseXmlSerializer = true; \/\/ global setting for all types\n        config.Formatters.XmlFormatter.SetSerializer&lt;ComplexObject>(new XmlSerializer(typeof(ComplexObject))); \/\/ overriding just for one type<\/code><\/pre>\n<h2 class=\"wp-block-heading\">Setting order <\/h2>\n<p>Yet another option to deal with ASP.NET XML serialisation issues would be to define property order explicitly:<\/p>\n<pre class=\"wp-block-code\"><code class=\"\">[DataContract(Name = \"ComplexObject\", Namespace = \"\")]\npublic class ComplexObject\n{\n    [DataMember(Order = 1)]\n    public int Id { get; set; }\n    [DataMember(Order = 2)]\n    public string Name { get; set; }\n    [DataMember(Order = 3)]\n    public string Location { get; set; }\n    [DataMember(Order = 4)]\n    public string Reference { get; set; }\n    [DataMember(Order = 5)]\n    public double Rate { get; set; }\n    [DataMember(Order = 6)]\n    public double DiscountedRate { get; set; }\n}<\/code><\/pre>\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n<p>XML serialisation has been around since the beginning of .NET. And even though it may seem that JSON has taken over, XML isn&#8217;t going anywhere any time soon. It is good to know we have many ways to deal with it should we ever need to. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>A client reached out to us with a weird problem. Their ASP.NET WebAPI project (somewhat legacy tech) needed to communicate with an application running on a mainframe (dinosaur-grade legacy tech). But they were having XML serialisation issues&#8230; They had a test XML payload, but only half of that kept coming across the wire: broken serialisation &hellip; <a href=\"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;ASP.NET XML serialisation issues: observations on DataContractSerializer&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":360,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[11],"tags":[12],"class_list":["post-1069","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dev","tag-c"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>ASP.NET XML serialisation issues: observations on DataContractSerializer - Timur and associates<\/title>\n<meta name=\"description\" content=\"This article captures our research on specific ASP.NET XML serialisation issues to do with DataContractSerializer quirk\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"ASP.NET XML serialisation issues: observations on DataContractSerializer - Timur and associates\" \/>\n<meta property=\"og:description\" content=\"This article captures our research on specific ASP.NET XML serialisation issues to do with DataContractSerializer quirk\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/\" \/>\n<meta property=\"og:site_name\" content=\"Timur and associates\" \/>\n<meta property=\"article:published_time\" content=\"2021-11-12T05:07:06+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-07T11:48:42+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2020\/02\/helloquence-5fNmWej4tAA-unsplash-scaled-e1581823690656.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"2560\" \/>\n\t<meta property=\"og:image:height\" content=\"1292\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"timur\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@TimurKh\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/\"},\"author\":{\"name\":\"timur\",\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/#\\\/schema\\\/person\\\/34d0ed30d573b5bc317ea990bd2e0c59\"},\"headline\":\"ASP.NET XML serialisation issues: observations on DataContractSerializer\",\"datePublished\":\"2021-11-12T05:07:06+00:00\",\"dateModified\":\"2026-03-07T11:48:42+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/\"},\"wordCount\":328,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/helloquence-5fNmWej4tAA-unsplash-scaled-e1581823690656.jpg\",\"keywords\":[\"c#\"],\"articleSection\":[\"Development\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/\",\"url\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/\",\"name\":\"ASP.NET XML serialisation issues: observations on DataContractSerializer - Timur and associates\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/helloquence-5fNmWej4tAA-unsplash-scaled-e1581823690656.jpg\",\"datePublished\":\"2021-11-12T05:07:06+00:00\",\"dateModified\":\"2026-03-07T11:48:42+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/#\\\/schema\\\/person\\\/34d0ed30d573b5bc317ea990bd2e0c59\"},\"description\":\"This article captures our research on specific ASP.NET XML serialisation issues to do with DataContractSerializer quirk\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/#primaryimage\",\"url\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/helloquence-5fNmWej4tAA-unsplash-scaled-e1581823690656.jpg\",\"contentUrl\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/wp-content\\\/uploads\\\/2020\\\/02\\\/helloquence-5fNmWej4tAA-unsplash-scaled-e1581823690656.jpg\",\"width\":2560,\"height\":1292},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/index.php\\\/2021\\\/11\\\/12\\\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"ASP.NET XML serialisation issues: observations on DataContractSerializer\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/#website\",\"url\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/\",\"name\":\"Timur and associates\",\"description\":\"Notes of an IT contractor\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/blog.wiseowls.co.nz\\\/#\\\/schema\\\/person\\\/34d0ed30d573b5bc317ea990bd2e0c59\",\"name\":\"timur\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/23d55e17d4f0990ee4d12bc6e5dcfb58a292934efd62a185756876379e780b16?s=96&r=pg\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/23d55e17d4f0990ee4d12bc6e5dcfb58a292934efd62a185756876379e780b16?s=96&r=pg\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/23d55e17d4f0990ee4d12bc6e5dcfb58a292934efd62a185756876379e780b16?s=96&r=pg\",\"caption\":\"timur\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/TimurKh\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"ASP.NET XML serialisation issues: observations on DataContractSerializer - Timur and associates","description":"This article captures our research on specific ASP.NET XML serialisation issues to do with DataContractSerializer quirk","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/","og_locale":"en_US","og_type":"article","og_title":"ASP.NET XML serialisation issues: observations on DataContractSerializer - Timur and associates","og_description":"This article captures our research on specific ASP.NET XML serialisation issues to do with DataContractSerializer quirk","og_url":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/","og_site_name":"Timur and associates","article_published_time":"2021-11-12T05:07:06+00:00","article_modified_time":"2026-03-07T11:48:42+00:00","og_image":[{"width":2560,"height":1292,"url":"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2020\/02\/helloquence-5fNmWej4tAA-unsplash-scaled-e1581823690656.jpg","type":"image\/jpeg"}],"author":"timur","twitter_card":"summary_large_image","twitter_creator":"@TimurKh","schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/#article","isPartOf":{"@id":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/"},"author":{"name":"timur","@id":"https:\/\/blog.wiseowls.co.nz\/#\/schema\/person\/34d0ed30d573b5bc317ea990bd2e0c59"},"headline":"ASP.NET XML serialisation issues: observations on DataContractSerializer","datePublished":"2021-11-12T05:07:06+00:00","dateModified":"2026-03-07T11:48:42+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/"},"wordCount":328,"commentCount":0,"image":{"@id":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2020\/02\/helloquence-5fNmWej4tAA-unsplash-scaled-e1581823690656.jpg","keywords":["c#"],"articleSection":["Development"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/","url":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/","name":"ASP.NET XML serialisation issues: observations on DataContractSerializer - Timur and associates","isPartOf":{"@id":"https:\/\/blog.wiseowls.co.nz\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/#primaryimage"},"image":{"@id":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2020\/02\/helloquence-5fNmWej4tAA-unsplash-scaled-e1581823690656.jpg","datePublished":"2021-11-12T05:07:06+00:00","dateModified":"2026-03-07T11:48:42+00:00","author":{"@id":"https:\/\/blog.wiseowls.co.nz\/#\/schema\/person\/34d0ed30d573b5bc317ea990bd2e0c59"},"description":"This article captures our research on specific ASP.NET XML serialisation issues to do with DataContractSerializer quirk","breadcrumb":{"@id":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/#primaryimage","url":"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2020\/02\/helloquence-5fNmWej4tAA-unsplash-scaled-e1581823690656.jpg","contentUrl":"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2020\/02\/helloquence-5fNmWej4tAA-unsplash-scaled-e1581823690656.jpg","width":2560,"height":1292},{"@type":"BreadcrumbList","@id":"https:\/\/blog.wiseowls.co.nz\/index.php\/2021\/11\/12\/asp-net-xml-serialisation-issues-observations-on-datacontractserializer\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.wiseowls.co.nz\/"},{"@type":"ListItem","position":2,"name":"ASP.NET XML serialisation issues: observations on DataContractSerializer"}]},{"@type":"WebSite","@id":"https:\/\/blog.wiseowls.co.nz\/#website","url":"https:\/\/blog.wiseowls.co.nz\/","name":"Timur and associates","description":"Notes of an IT contractor","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.wiseowls.co.nz\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blog.wiseowls.co.nz\/#\/schema\/person\/34d0ed30d573b5bc317ea990bd2e0c59","name":"timur","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/23d55e17d4f0990ee4d12bc6e5dcfb58a292934efd62a185756876379e780b16?s=96&r=pg","url":"https:\/\/secure.gravatar.com\/avatar\/23d55e17d4f0990ee4d12bc6e5dcfb58a292934efd62a185756876379e780b16?s=96&r=pg","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/23d55e17d4f0990ee4d12bc6e5dcfb58a292934efd62a185756876379e780b16?s=96&r=pg","caption":"timur"},"sameAs":["https:\/\/x.com\/TimurKh"]}]}},"_links":{"self":[{"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/posts\/1069","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/comments?post=1069"}],"version-history":[{"count":9,"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/posts\/1069\/revisions"}],"predecessor-version":[{"id":1362,"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/posts\/1069\/revisions\/1362"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/media\/360"}],"wp:attachment":[{"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/media?parent=1069"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/categories?post=1069"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.wiseowls.co.nz\/index.php\/wp-json\/wp\/v2\/tags?post=1069"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}