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.
The EntityDataSource does not seem to provide much customizability at all, e.g. you can’t seem to be able to tweak the insert/update commands(or you don’t have to?). Do professionals mostly write raw Linq code to use in conjunction with Databound controls like Repeater?
It depends on the scenario.
If you need a grid-like control, where users can view/edit/delete records (basically allowing them to directly modify DB records), then use a LinqDataSource.
If you want more control over the queries use Repeater and bind to a concrete
List<T>(for example).I prefer the latter, because it isolates logic into a DAL, where it can be tested and controlled more efficiently.