Previously: Architecting Linq to SQL, part 9 End of the line This is intended to be the last part in this series and I wanted to take the opportunity to talk about a number of related if diverse topics. I would like to look at what I would like to see in the next version, and talk about when and where...

Previously: Architecting LINQ To SQL part 8 LINQ To SQL with N-Tier: Why is there pain? People tend to experience pain using LINQ in N-Tier scenarios because they are trying to pass entities between layers. You can find some examples of this complaint, not to pick on anyone but just to avoid repeating...

Previously: Architecting LINQ To SQL Applications, part 7 Tiers A layer, such as we discussed Part 2 , in is not a tier. A layer is a logical unit of division; a tier is a physical unit of division. The two need not be the same. Software may be layered within a single process running on one machine or...