Choosing the Right LINQ Model for Your Application

Posted By: Bob Familiar | Nov 14th, 2007 @ 3:19 PM | 10,270 Views | 5 Comments

Bill Zack presents an Architect Point of View (arcPOV) presentation on selecting the right LINQ model for your application. Bill covers 3 different flavors of LINQ; LINQ to SQL, LINQ to Datasets, and LINQ to Entities. Bill discusses how these flavors of LINQ can be used to access data in relational databases. He then covers the differences and the trade-offs involved in choosing between them.
Media Downloads:
Rating:
0
0
#Nov 30th, 2007 @ 10:09 AM
evildictaitor
evildictaitor
if( !succeed( try() ) ) { while(true) try(); }
What? No download button?

How woode.
#Nov 30th, 2007 @ 11:39 AM
RomSteady
RomSteady
Kimono's rock...
You could always right-click on the "Full Screen" link and pick "Save Target As..."  Wink
#Dec 1st, 2007 @ 7:01 AM
odujosh
odujosh
Need Microsoft SUX now!

You go one thing wrong:
You said Linq to Dataset is the only one that supports change tracking.

Linq to SQL also does. Only reason to use LINQ to Dataset is if you have a bunch of datasets laying around from ADO.NET 2.0 work.

#Dec 1st, 2007 @ 8:17 PM
JoshRoss
JoshRoss
A righteous infliction of retribution manifested by an appropriate agent.
Channel9 Wishlist item: Silverlight encode the screencasts. Thanks ahead of time, Josh Ross, Devoted Niner.
#Dec 11th, 2007 @ 12:47 PM
wzack
wzack
Bill Zack
odujosh is absolitely correct.  The main advantage of LINQ to Datasets is if you have a lot of them because your applications already depend on them heavily.
Microsoft Communities