Migrating from Entity Framework 4 is a modern and promising approach to SQL Server database. It is the basis for WCF data services, and the idea of a conceptual model will be displayed in another Microsoft product, of course (Reporting Services and others, possibly).
And that gives you a lot of hooks that let you execute SQL statements on the fly, and you can integrate stored procedures very well in the Entity Framework.
And for the "run of the mill" everyday tasks, it gives you good C # objects - based on your database - for work.
In my opinion, this is your best choice at the moment - and the one that has the most flexibility and capabilities. You can start with a database (first “database”) and create your classes from existing tables; or you can start with a model and have EF4 to generate your database for you, and EF v4.1 (expected quite soon) will also offer a “code first” development where you don't even need a visual model, but you can describe all your objects databases and settings only in C # code.
Update:
marc_s
source share