Narrowing ORM options for the sake of sanity
"The right tool for the job" or so the saying goes which I don’t believe can be applied to a choice between LINQ to SQL and the Entity Framework. Currently I am evaluating the virtues of Entity Framework over LINQ To
SQL; why not use both I hear you say? Well I have already reached the point in the evaluation to know that there is not enough separating them to make me consider maintaining skills in both and considering that all Microsoft’s serious investment is going into the Entity Framework then the choice is made that much easier.
I have found to date that I can continue with using the Repository approach along with the Specification Pattern (for dynamic querying) and Fetching Strategies and that was a big criteria for me. There are of course some lingering frustrations with Version 1.0 however at this point I am satisfied that the Entity Framework team will address those in subsequent releases and for the moment I will endure.
