Sign In| Join
Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jan 05, 2012 05:30 PM by atconway
Participant
1656 Points
1345 Posts
Jan 04, 2012 02:01 AM|LINK
using vs 2010.
what are the pros and cons of using queries in LINQ vs ADO.Net (stored procs).
thanks
MC
Star
10540 Points
1704 Posts
Jan 04, 2012 02:50 AM|LINK
This post covers it fairly well:
http://stackoverflow.com/questions/2698151/entity-framework-vs-linq-to-sql-vs-ado-net-with-stored-procedures
8277 Points
1435 Posts
Jan 04, 2012 11:41 AM|LINK
Hi,
here are two additional sites which should help you:
All-Star
16846 Points
2756 Posts
Jan 05, 2012 05:30 PM|LINK
@MyronCope - the only thing I will add is be aware that LINQ to SQL (not LINQ in general) fizzled fast at MSFT and is not the flagship ORM; The Entity Framework is. In fact I heard almost 2 years ago now that LINQ to SQL was not going to be enhanced but only supported (read here: http://blogs.msdn.com/b/adonet/archive/2008/10/29/update-on-linq-to-sql-and-linq-to-entities-roadmap.aspx)
EF is still backed by ADO.NET so my recommendation is to either use raw ADO.NET or the Entity Framework and not go so much for LINQ to SQL regardless of the comparisons due to the above information.
MyronCope
Participant
1656 Points
1345 Posts
ado.net vs. LINQ
Jan 04, 2012 02:01 AM|LINK
using vs 2010.
what are the pros and cons of using queries in LINQ vs ADO.Net (stored procs).
thanks
MC
tehremo
Star
10540 Points
1704 Posts
Re: ado.net vs. LINQ
Jan 04, 2012 02:50 AM|LINK
This post covers it fairly well:
http://stackoverflow.com/questions/2698151/entity-framework-vs-linq-to-sql-vs-ado-net-with-stored-procedures
Horizon_Net
Star
8277 Points
1435 Posts
Re: ado.net vs. LINQ
Jan 04, 2012 11:41 AM|LINK
Hi,
here are two additional sites which should help you:
If my post solves your problem, please mark as answer.
atconway
All-Star
16846 Points
2756 Posts
Re: ado.net vs. LINQ
Jan 05, 2012 05:30 PM|LINK
@MyronCope - the only thing I will add is be aware that LINQ to SQL (not LINQ in general) fizzled fast at MSFT and is not the flagship ORM; The Entity Framework is. In fact I heard almost 2 years ago now that LINQ to SQL was not going to be enhanced but only supported (read here: http://blogs.msdn.com/b/adonet/archive/2008/10/29/update-on-linq-to-sql-and-linq-to-entities-roadmap.aspx)
EF is still backed by ADO.NET so my recommendation is to either use raw ADO.NET or the Entity Framework and not go so much for LINQ to SQL regardless of the comparisons due to the above information.