“Speed O/R Mapping with LINQ to SQL” by Roger Jennings for the December 2008 issue carries the following deck:
LINQ to SQL continues to be a top contender in the .NET object/relational mapping tool market despite Microsoft's promotion of the Entity Framework as one of the "Pillars of SQL Server 2008: Dynamic Development."
The article includes a table that compares LINQ to SQL and Entity Framework features and a “Visual Studio 2008 SP1 Add-Ins Remove LINQ to SQL Roadblocks” sidebar that describes Huageti Systems’ DBML/EDMX Tools utility for LINQ to SQL and Entity Framework and Damien Guard’s T4 template for customizing LINQ to SQL partial class code generation.
Following are recent OakLeaf blog posts that relate to the story:
- Entity Framework Team Abandons Unified N-Tier Architecture for v2 (11/21/2008)
- Microsoft Responds to LINQ to SQL Bug Report after Its First Anniversary (11/21/2008)
- Forcing Gratuitious Pluralization of EF EntitySet Names Was a Very Bad Decision (9/21/2008)
- Singularizing EntityType and Pluralizing EntitySet Names with the Huagati DBML/EDMX Tools (9/21/2008)
- Is the ADO.NET Team Abandoning LINQ to SQL? (5/23/2008)
And here are a two minor corrections to the story:
- In the main text, “Hibernate and NHibernate” should be preceded by “Java and .NET purists” as Hibernate is a Java O/RM tool.
- In Table 1’s feature “Model-first design” for LINQ to SQL, “Not available” should read “Create Database supported”.
Note: The latest version of Huagati’s DBML/EDMX Tools support incremental modifications to the database schema underlying a LINQ to SQL project.