Choosing the Right LINQ Model for Your Application
- Posted: Nov 14, 2007 at 3:19 PM
- 11,150 Views
- 5 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
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.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
How woode.
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.
Remove this comment
Remove this thread
close