As you correctly observed in the answer to your own question, removing the “virtual” keyword from the collection properties works around the problem, by preventing the Entity Framework from creating a change tracking proxy. However, this is not a solution for many people, because change tracking proxies can be really convenient and can help prevent … Read more
I would claim that, like most things, its a sliding scale. There are things that we make that want to have the property of persistence. On one end of the scale is this thing having all of the guts, dependencies, and code that is custom built to persist just this one thing in its particular … Read more
Having one big EDM containing all the entities generally is NOT a good practice and is not recommended. Using one large EDM will cause several issues such as: Performance Issue in Metadata Load Times: As the size of the schema files increase, the time it takes to parse and create an in-memory model for this … Read more
A different approach is to hook into the ObjectMaterialized event in the DbContext and set the kind there. In my DbContext constructor, i do this: ((IObjectContextAdapter)this).ObjectContext.ObjectMaterialized += new ObjectMaterializedEventHandler(ObjectMaterialized); and then the method looks like this: private void ObjectMaterialized(object sender, ObjectMaterializedEventArgs e) { Person person = e.Entity as Person; if (person != null) // the … Read more
This is a common confusion. The opposite of lazy loading is: no loading unless you explicitly do the loading yourself (e.g. by eager loading using Include). So if you turn off lazy loading in any way — removing the virtual modifier is one of them — the behaviour does not turn into eager loading but … Read more
I would append another view: POCO states for objects which are not dependent on any framework. The wiki definition of a POJO is much more meaningful to me then the one for POCO: http://en.wikipedia.org/wiki/Plain_Old_Java_Object To paraphrase the wiki definition of the POJO, we can say that POCO object might not be forced to: I. Extend … Read more
I’ve accepted @jfar’s answer because he put me on the right track, but thought i’d add an answer here for other people’s benefit. The reason the relationships were not getting updated is for the following reasons: 1) Completely disconnected scenario. ASP.NET = stateless, new context newed up each HTTP request. 2) Edited entity created by … Read more
Here is how I just got EF 4.1 (RC) to do table splitting in Code First. Define your two entities. Make sure to include the key in both entities. Also, include navigation properties in each entity pointing to the other entity. In your OnModelCreating override . . . a. Map both entities to the same … Read more
for future reference: you can use data annotations MSDN EF – Code First Data Annotations [NotMapped] public string AddressAs { get; set; }
XmlSerializer is one way to do it. DataContractSerializer is another. Example with XmlSerializer: using System.Xml; using System.Xml.Serialization; //… ShoppingCart shoppingCart = FetchShoppingCartFromSomewhere(); var serializer = new XmlSerializer(shoppingCart.GetType()); using (var writer = XmlWriter.Create(“shoppingcart.xml”)) { serializer.Serialize(writer, shoppingCart); } and to deserialize it back: var serializer = new XmlSerializer(typeof(ShoppingCart)); using (var reader = XmlReader.Create(“shoppingcart.xml”)) { var shoppingCart = … Read more