Data access layer using Linq to SQL
- by Andrei Tanasescu
I am building a c# - linq - sql server winforms/asp.net application, accessing a database. I would like my business logic layer to be easily testable, and that means not littering it with Linq database queries everywhere. What design patterns/ best practices are available for the following use cases
- inserting/updating a new object
- searching for an object
- loading a bunch of related data into a sort of "presentation" object that could be displayed by various views ?