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.
I guess I’m old school, when I architect a project I still think of writing a database layer that includes use of objects like datareaders and datasets… But it seems to me that Microsoft had to come up with better tools since my last project in 2.0, something that would hide all the pipping labor and keep the developer focused on writing logic, or at least less plumbing code.
How is that done with 3.5 ?
Thanks,
Yann
Well…Don’t discount your experience with datasets and readers yet 😉
You might like to look at Linq to Entities or things like NHibernate and other ORM’s. But don’t let the hype carry you away, evaluate them against your requirements, you may just find that you still come back to Datasets and readers in some cases.