DotNetStories
In this post I am going to provide you with a hands-on example on how to avoid writing your LINQ to Entities queries in a way that will hinder performance of your application. The aim of this post (hopefully a series of posts on performance and Entity Framework) is to highlight bad coding practices when architecting an applications that uses EF as the ORM to fetch and manipulate data from the data store. I am going to point out some practises and patterns that very often developers use and cause EF to create poor-performing T-SQL statements.
In this post I am going to provide you with a hands-on example on how to handle efficiently batch operations with Entity Framework and the EF Utilities library.
This is a post relevant to all the developers out there
that use Web Forms as their main ASP.Net
platform.
This is going to be the tenth post of a series
of posts regarding ASP.Net and the Entity Framework and
how we can use Entity Framework to access our
datastore. You can find the first one here,
the second one here , the third one here , the
fourth one here, the fifth one here ,the sixth one here ,the seventh one here ,the
eighth one here
and the ninth one
here.