stefanoricciardi.com VS.

tushar-mehta.com

The Problem of Circular ReferencesRecently I had to model a tree-like structure using a variation of the GoF composite design pattern and to pass this class to a WCF service for further processing. The class has circular reference as described by the following drawing: Therefore off I went to naively create my DataContract along the following lines:[DataContract(Namespace = "http://schemas.acme.it/2009/10"]public class Node{ [DataMember(Name="Children", Order=2)] private IList children; [DataMember(Name="Id", Order=0)] public string Id { get; set; } [DataMember(Name="Parent", Order=1)] public Node Parent { get; set; } public Node() { children = new List() } public void AddChild(Node node) { this.children.Add(node); node.Parent = this; } public IList Children { get { IList result = new List(this.children); foreach (Node child in this.children) { foreach (Node innerChild in child.Children) { result.Add(innerChild); } } return result; } }}Unfortunately at run time I was greeted by the following exception: Object graph for type 'System.Collections.Generic.List`1[[Node ...]]' contains cycles and cannot be serialized if reference tracking is disabled.The SolutionReading around I realized that up until some time ago you had to implement your own DataContractSerializer (see for example this post by Sowmy Srinivasan). Luckily, it turns out that with NET 3.5 SP1 everything is much simpler: you just have to use the IsReference parameter in the DataContract attribute, as follows:[DataContract(Namespace = "http://schemas.acme.it/2009/10", IsReference=true)]public class Node{ // everything same as in the example above.}The CatchFor some reason, if you turn on the IsReference attribute, then you cannot set the IsRequired attri