Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Are there more extension points available in linq-to-sql than creating your own partial DataContext class and extension methods?
Update:
To be more specific: I want to collect the extension points that are available in Linq-to-Sql, because I thought it would be interesting to know were you are able to step into the codegeration.
At the moment I got:
In what sense? If you mean lower-level constructs where you can abstract away the database, I believe the answer to that is “no”, and you’d have to use the Entity Framework to write a Provider to do so.
If you mean on the classes themselves, you can implement partial methods on the DataContext AND your model classes, which is really powerful, in addition to extending the classes any way you want simply by adding new methods.