One of the features that I don't see used often enough is the ability to add your own properties and methods to an existing ADO.NET Entity Model through the magic of partial classes. I show some samples of why I use this feature extensively.
I've been evaluating the ADO.NET Entity Framework as something that I might want to replace my existing DLINQ (LINQ to SQL) code. In this article, I'll point out a bone of contention I have with EF and ORMs in general.
In this article, I will be comparing the Object-Relational Modeling features of Rails w/ActiveRecord to the ADO.NET Entity Framework w/LINQ to Entities
This post will compare and contrast LINQ to SQL and LINQ to Entities provided by ADO.NET vNext, giving some information on the situations in which each technology shines and where they don't.
This post will compare and contrast the features of just using raw DLinq and SQLmetal-generated classes with the ADO.NET Entity Framework. I'll also show how the two can work together