I’m mostly a NHibernate user, but EF code first approach is intriguing, especially in situation where the customer prefer to use only Microsoft Stack libraries, thus EF 5.0 is a good approach to write quickly an Efficient data access module in really few clicks. Enabling EF5 on your own project is as simple as adding […]

Continue reading about Entity Framework 5.0, first steps and impressions

One of the most annoying problem with the first version of entity Framework is that you have barely no option other than go with “Database First approach”, and when you start mapping database views your life started to become difficult. The first obvious problem is that the designer, during the import phase from database, try […]

Continue reading about Entity Framework error 3002 on views when model updated

Part 1: First Steps Part 2: Managing Relations Relations between objects are not limited to an object that keep a reference to another object (as seen in part 2), but I can have an object that contains a list of other objects. This is the classic RDBMS rough equivalent of the One-To-Many relation. I decided […]

Continue reading about Entity Framework 4.1–Collection Relations

Entity Framework is quite a good product, but in my opinion still misses some point to be called an ORM. I must admit that I never used the 4.1 Code first in real project, but there are some stuff that still does not convince me when using EF. When I decide to use EF (and […]

Continue reading about Entity Framework, a super dataset?

EF 4.1 is now in RC phase and as a NHibernate user I’m curious to check the fluent API to map entities to database. One of the feature that I and Andrea miss most is the possibility to map private properties with fluent interface. It seems strange to map private properties at once, but it […]

Continue reading about Mapping private properties with EF 4.1 RC and Fluent mapping