Best way to use Linq2Sql?

Question

I'm struggling to think of a good way to use linq2sql, simply I want to use it, but I can't figure out whether it's best to wrap up the linq2sql generated classes inside my model classes providing some form of generic abstract base class / or interface for the common methods on my model classes like add, update, delete etc, or to extend the partial classes that linq2sql generated.

What design have people found most successful? and could you give a quick run down of those said designs?

(I know this is kind of subjective because everyone will have their own best ways, however , I'm not sure if it should be tagged as so. Feel free to edit and make a community wiki if you think it should be.)

Answer 1

Personally, I wrap Linq2SQL in the repository pattern.

Answer 2

Check this article:

A simple Business Object wrapper for LINQ to SQL

Answer 3

Depending on the complexity of your application you may or may not need to use anything other than the generated classes for your ORM. I find that I am able to happily live with the generated classes, extended by partial methods and by wrapping the data context with a wrapper (and possibly extended if I need to add common functionality) to improve testability. Most of my applications are relatively simple from a database perspective, though.