Entity Framework VS LINQ to SQL VS ADO.NET with stored procedures?
Posted
by BritishDeveloper
on Stack Overflow
See other posts from Stack Overflow
or by BritishDeveloper
Published on 2010-04-23T11:36:37Z
Indexed on
2010/04/23
11:43 UTC
Read the original article
Hit count: 302
How would you rate each of them in terms of:
- Performance
- Speed of development
- Neat, intuitive, maintainable code
- Flexibility
- Overall
I like my SQL and so have always been a die-hard fan of ADO.NET and stored procedures but I recently had a play with Linq to SQL and was blown away by how quickly I was writing out my DataAccess layer and have decided to spend some time really understanding either Linq to SQL or EF... or neither?
I just want to check, that there isn't a great flaw in any of these technologies that would render my research time useless. E.g. performance is terrible, it's cool for simple apps but can only take you so far
© Stack Overflow or respective owner