What to be Expecting of Entity Framework in .NET 4
The ADO.NET team started
to release a series of posts
that describe the primary
scenarios and patterns they have
been working on throughout the
new release of Entity Framework
in .NET 4.0. The primary scenarios and
patterns you should be expecting:
- Model First development –
Enables the developer to start develop the model and then
have T-SQL and customized code generated from that model.
- Enable testing applications with Entity Framework –
A new interface was added, along with guidance, that enables better
testability of applications that use the Entity Framework.
- Persistence Ignorance –
Enabling developers to use their own classes without the need to introduce
interfaces or other elements specific to the Entity Framework.
- Applications Patterns –
Discussing patterns like the Repository and UnitOfWork patterns with
guidance on how to use them with the Entity Framework.
- N-Tier applications with the Entity Framework –
Adding API’s and templates that make building N-Tier applications with
the Entity Framework much easier.
Entity Framework Improvements
- Customization of Code Generation –
Integration with the ADO.NET Entity Framework Designer and T4 Templates
in Visual Studio to provide developer controlled code generation.
- Small things that make development of applications simpler –
Add things like Pluralization and Singularlization in the model,
lazy loading, and more stored procedure mapping make building
applications that use the Entity Framework much easier.
- Customizing Queries –
Support for existing LINQ operators, recognizing a larger set of
patterns with LINQ, writing model defined functions along with the ability
to use these in LINQ, and a number of other ways to create and customize queries.
- SQL Generation Readability Improvements –
Improve the readability, along with T-SQL performance optimizations, of the
- Bug fixes and more.
Lets sum up, a lot can be expected of the new Entity Framework release.
The ADO.NET team try to approach a lot of things that raised while developing
with Entity Framework V1. You can read the following posts for more details: