POCO Object Structure

Question

What can be done by creating POCO using T4 templates in entity infrastructure 4.0? Why doesn't the default behavior when using the framework 4.0 entity create POCO?

Answer 1

You lose a lot of things. POCO PURE is limited in ORM because it will not track changes. In other words, when you mutate an object and then save changes to the context, you want the changed properties to be stored in the database. With pure POCO, you can do this with change tracking based on snapshots, which is pretty inefficient. You can also do this with runtime proxies that force you to create track properties public virtual, so you may not have "POCO". In addition, using a proxy means that you do not know the true type of instance runtime.

You will also lose some convenient properties, such as EntityState.

"" POCOs . , -, , , -, "" POCO.

, Entity Framework POCO, ORM. , POCO LINQ, . , "" POCOs Entity Framework, .