Just would like to know if you guys considered converting over to entity framework or not

share|improve this question
2  
Can you think of a good reason to? Neither can I. –  ChaosPandion Apr 3 '10 at 4:15
    
L2S is more performant that EF. If L2S fulfills requirements of a job it is a much better choice than EF. IMO –  Sky Sanders Apr 3 '10 at 7:22
add comment

1 Answer

This is definitely one of the more liberal definitions of feature-request that I've come across. Private implementation decisions are not exactly features; we shouldn't care any more about whether they use Linq to SQL or Entity Framework than we should about whether or not their pagination algorithm uses a Quicksort or a Merge Sort.

If it ain't broke, don't fix it.

Full disclosure: I personally use Linq to SQL in a number of apps and will convert them over to the Entity Framework when you pry the keyboard from my cold dead fingers.

share|improve this answer
    
The question body is different from the title... I'm going to edit to clarify. –  Jon Seigel Apr 3 '10 at 4:38
add comment

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .