object-graph

There is a class Company , which has reference to another instance of Company to represent the parent . Lets say there are four companies c1 , c2 , c3 & c4 and c2 , c3 , c4 has parent company set as c1 . For example: public class Company { public Company parent; public Company() { } public Company(Company parent) { this.parent = parent; } public static void main(String[] args) { Company c1 = new Company(); Company c2 = new Company(c1); Company c3 = new Company(c1); Company c4 = new Company(c1); } If we set c2 as parent company of the c1 : c1.parent = c2; then it will create a Cyclomatic

I'm having difficulty conditionally creating a dependency. Googling, I have yet to find a good example of using the BuildStack and Conditional Predicates. Here's what I'm doing in the Registry: //snip public SomeRegistry() { this.InstanceOf<IFoo>().Is.Conditional( c => { c.TheDefault.Is.ConstructedBy(() => new FooZ()); c.If( p => p.ParentType.IsAssignableFrom(typeof(IBar)) && p.BuildStack.Current.RequestedType.IsAssignableFrom(typeof(IDoStuffWithFooA))) .ThenIt.Is.ConstructedBy(() => new FooA()); c.If( p => p.ParentType.IsAssignableFrom(typeof(IBar)) && p.BuildStack.Current.RequestedType

While using this code to serialize an object: public object Clone() { var serializer = new DataContractSerializer(GetType()); using (var ms = new System.IO.MemoryStream()) { serializer.WriteObject(ms, this); ms.Position = 0; return serializer.ReadObject(ms); } } I have noticed that it doesn't copy the relationships. Is there any way to make this happen? Simply use the constructor overload that accepts preserveObjectReferences , and set it to true: using System; using System.Runtime.Serialization; static class Program { public static T Clone<T>(T obj) where T : class { var serializer = new

In our app under development we are using Core Data with a sqlite backing store to store our data. The object model for our app is complex. Also, the total amount of data served by our app is too large to fit into an iOS (iPhone/iPad/iPod Touch) app bundle. Because of the fact that our users are, typically, interested only in a subset of the data, we've partitioned our data in such a way that the app ships with a subset (albeit, ~100 MB) of the data objects in the app bundle. Our users have the option of downloading additional data objects (of size ~5 MB to 100 MB) from our server after they