Linked by Thom Holwerda on Sun 12th Jul 2009 21:29 UTC
Thread beginning with comment 373087
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.




Member since:
2006-01-01
ADO.Net is actually extremely good at what it does - it is just a bad idea. It has one model - data is snapshotted and a local view is taken. This works really well for Webservices and Web, as you really, really should not be directly poking database tables on a web page, but when it comes to desktop, it is clunky. I did far too many years of Delphi to be happy with a non live data access model. ADO.Net skirts the issue by making updates fairly painless, but it is trying to solve the problem of concurrent data access with a sledge hammer like approach. Then again, you need to go with the lowest common feature set if you want to be generic, and this will be why they did it the way they did.
What you find yourself doing is writing your own wrapper and using that everywhere. This is what I did and it has travelled through two separate jobs and countless projects.