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
Here is a working example. Keypoints are: Declaration of Accounts Use of JsonProperty attribute . using (WebClient wc = new WebClient()) { var json = wc.DownloadString(“http://coderwall.com/mdeiters.json”); var user = JsonConvert.DeserializeObject<User>(json); } – public class User { /// <summary> /// A User’s username. eg: “sergiotapia, mrkibbles, matumbo” /// </summary> [JsonProperty(“username”)] public string Username { get; set; … Read more
Plain old CLR object
POCOs(Plain old CLR objects) are simply entities of your Domain. Normally when we use entity framework the entities are generated automatically for you. This is great but unfortunately these entities are interspersed with database access functionality which is clearly against the SOC (Separation of concern). POCOs are simple entities without any data access functionality but … Read more
If you want to take full advantage of ORM you will definitely use Entity reference: public class Order { public int ID { get; set; } public Customer Customer { get; set; } // <– Customer object … } Once you generate an entity model from a database with FKs it will always generate entity … Read more
Let’s try it this way: Attach BlogPost to context. After attaching object to context the state of the object, all related objects and all relations is set to Unchanged. Use context.ObjectStateManager.ChangeObjectState to set your BlogPost to Modified Iterate through Tag collection Use context.ObjectStateManager.ChangeRelationshipState to set state for relation between current Tag and BlogPost. SaveChanges Edit: … Read more
These articles might be of interest…the series really gets into the advantages and disadvantages of a POCO approach. Link Link Link In these articles the author mentions future articles that describe best practices in implementing Repository and Unit of Work patterns, but I can’t find them. These articles are well written and I’d like to … Read more
“Plain Old C# Object” Just a normal class, no attributes describing infrastructure concerns or other responsibilities that your domain objects shouldn’t have. EDIT – as other answers have stated, it is technically “Plain Old CLR Object” but I, like David Arno comments, prefer “Plain Old Class Object” to avoid ties to specific languages or technologies. … Read more
A POCO follows the rules of OOP. It should (but doesn’t have to) have state and behavior. POCO comes from POJO, coined by Martin Fowler [anecdote here]. He used the term POJO as a way to make it more sexy to reject the framework heavy EJB implementations. POCO should be used in the same context … Read more