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.

Microsoft has unleashed two more codenames on the unsuspecting public - Jasper and Astoria. Are they worth paying attention to?

Microsoft has released a patch that fixes the missing "ADO.NET Entity Model" template from Orcas Beta 1

I've been re-reading blog entries, including some as early as 10-15 days ago, and they confirm the worst - EDM designer will NOT ship with Orcas RTM.

I found this screencast showing off the EDM designer that the Entity Framework so sorely needs. The problem? It won't ship with Orcas!

I've been following the development of C# 3.5 (or whatever-the-heck it will be called) as well as the Entity Framework for a while now. It looks as though this CTP finally integrates all the useful bits.

I recently wrote an article for Dr. Dobb's journal detailing a Web 2.0 project that I did with LINQ to SQL and an early CTP of ADO.NET vNext. The article is in the January 2007 edition of Dr. Dobb's.

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.

The August CTP of the ADO.NET Entity Framework is out!! Get it now, your life could depend on it!

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