-
The new support for POCO in Entity Framework seeks to enable better ways of coding application domain logic without polluting domain classes with persistence concerns. Persistence Ignorance can in fact improve maintainability, testability and evolvability of an application by making it possible...
-
In my previous article, I described a foundation on which you can build successful n-tier applications, focusing mainly on anti-patterns to avoid. There are many issues to consider before making decisions about the design of an n-tier application. In this article, I examine n-tier patterns for success...
-
【原文地址】 POCO in the Entity Framework : Part 2 – Complex Types, Deferred Loading and Explicit Loading 【原文发表日期】 28 May 09 09:03 AM 在上星期的贴子《 POCO Experience in Entity Framework 》 （ 实体框架中的POCO体验 ）中，我讨论了Entity Framework 4.0中POCO支持的基本。在这个贴子里，我将讨论与POCO相关的另外几个方面。 复杂类型（Complex Types） POCO中的复杂类型支持跟常规的基于 EntityObject...
-
Note: This article applies to beta software and comes with no warranty or support, use at your own discretion. You must have Visual Studio.Net 2010 Beta 1 installed on your machine to make use of the code. KandaAlpha now hosted on CodePlex, download from http://kandaalpha.codeplex.com/ This is an article...
-
In my MSDN Magazine article on SOA Data Access I recommend exposing Data Transfer Objects (DTOs) from the Data Access Layer (DAL). These objects should be Plain Old CLR Objects (POCOs) that are Persistent Ignorant (PI), eschewing traces of any particular persistence technology. (How’s that for an alphabet...
-
If you have been watching this blog, you know that I have been discussing the various aspects of POCO capabilities we added to Entity Framework 4.0. POCO support makes it possible to do persistence ignorance with Entity Framework in a way that was never possible with Entity Framework 3.5. If you missed...
-
In my last post on POCO , I mentioned the fact that there are two types of change tracking possibilities with POCO: Snapshot based Change Tracking and Notification based Change Tracking with Proxies. In this post, I would like to drill into both options a bit further and cover the advantages and...
-
EF4 Beta版增加了新的方法到ObjectContext。这些新APIs用来与EntityObjects、IPOCO、POCO实体配合工作： public partial class ObjectContext { ApplyCurrentValues 这个 API就像EF v1的 ApplyPropertyChanges 原理是从指定的对象获取标量属性值，并拷贝它们到带有相同EntityKey的对象中去。任何与初始值不同的值将被标记为Modified。例如 ， Customer customer_orig = new Customer { CustomerId = Guid.NewGuid...
-
Introduction My blog has been feeling very neglected after my move to the US and I thought with the recent release of Visual Studio 2010 / .Net Framework 4.0 Beta 1 it would be a good time to get back into a regular blogging rhythm. So for the first post I thought I’d run through a simple demo of the...
-
Spurred on both by the success of Damien Guard in using T4 to generate Linq to SQL code and of Jeff Reed from the EF team who built a prototype for using T4 to generate EF code, I recently hacked something up that makes it fairly easy to use T4 to generate EF classes. This is an early draft--there...
-
With EF4, it’s possible to execute some SQL queries. (It was possible with EF v1 with EF extensions ). I don’t like it. Indeed, it implies to break the EDM abstraction against the DataBase. Moreover, we can do without. In the V1, it was possible, with SSDL Functions, to write the SQL query...
-
【译者按】 Entity Framework 1.0 发布也有一段时间了，但感觉用的人很少。其中一个很大的原因，也许就是不支持POCO。要知道，Entity Framework 1.0的做法是让你的实体从EF的基类继承而来，这对很多人，特别是崇尚DDD的人来说，那是一副难以下咽的药啊。曾有微软开发人员提供了一个 POCO Adapter ，但那究竟不是正规的做法。Visual Studio 2010 和 .NET 4.0 提供了许许多多的新特性，真是让人激动，向往，大有一种回到.NET 1.0 刚出来时的感觉。春天啊（应该是夏天啊），你终于回来了（虽然早晨/晚上还是unseasonably冷）...
-
Last week I mentioned in the sneak preview on POCO that support for POCO entities is one of the new capabilities we have added to Entity Framework 4.0. This week, I’d like to go into the details of POCO support in Entity Framework 4.0. There’s quite a bit to discuss here, including: Overall POCO experience...
-
Better N-Tier Concurrency Management for the Entity Framework Posted in Technical at 11:03 am by Tony I just wrote an article for MSDN Magazine (due out in December) about developing n-tier applications for both LINQ to SQL and the Entity Framework. While researching the topic, I noticed a certain awkwardness...
-
Microsoft 已面向开发人员发布了两种旨在减少关系数据领域和面向对象的编程之间的阻抗失谐的产品：LINQ to SQL 和 ADO.NET Entity Framework。借助其中任何一种产品，您不必编写大部分探测代码，即可实现对象持久性。 本文使用以下技术： LINQ to SQL、ADO.NET Entity Framework和 SOA 迄今为止，Microsoft 已面向开发人员发布了两种旨在减少关系数据领域和面向对象的编程之间的阻抗失谐的产品：LINQ to SQL 和 ADO.NET Entity Framework。借助其中任何一种产品，您不必编写大部分探测代码，即可实现对象持久性...