LINQ to SQL vs ADO.NET
-
Hi, How ould you guys rate the 2 against each other? I would like to hear as many opinions as possible. If you have worked with both please comment on both. What is the difference in speed between the 2 seeing that ADO.NET uses stored procedures, and not sure if LINQ to SQL does as well? I have been working all my life with ADO.NET, is there a need to change to LINQ to SQL? Is there a future for LINQ to SQL? Brendan
-
Hi, How ould you guys rate the 2 against each other? I would like to hear as many opinions as possible. If you have worked with both please comment on both. What is the difference in speed between the 2 seeing that ADO.NET uses stored procedures, and not sure if LINQ to SQL does as well? I have been working all my life with ADO.NET, is there a need to change to LINQ to SQL? Is there a future for LINQ to SQL? Brendan
It gives a querying language very close to the normal .Net programming syntax. I can use the LINQ semantics across XML, normal objects and also SQL querying. LINQ's strongly typed feature allows me to eliminate hiccups at an early stage. You can have stored procedures in LINQ too. It is just a wrapper which finally converts the LINQ query to SQL statement to execute. You might want to have a look here - Link1[^], Link2[^], Link3[^] I have read about Linq to Entity being the recommended model in the future releases. You might want to have a look at it too.
-
Hi, How ould you guys rate the 2 against each other? I would like to hear as many opinions as possible. If you have worked with both please comment on both. What is the difference in speed between the 2 seeing that ADO.NET uses stored procedures, and not sure if LINQ to SQL does as well? I have been working all my life with ADO.NET, is there a need to change to LINQ to SQL? Is there a future for LINQ to SQL? Brendan
As my experienced , LINQ is easier than ADO.NET. Also, if you learn LINQ you can work with any Data Bases ( like SQL, XML, ... ) with the same query syntax.