My Rants and Raves about technology, programming, everything else...
After looking over the latest Data Access Block, i'll say it is better. But I still have my gripes:
On the whole though, I'd still recommend not using it and rolling your own DataAccess object with some of these ideas, but not most of them.
I have talked with many people over the last few years about my issues with the the Data Access Block, but it seems I've never enumerated my issues in 'print'. Here they are. If this has been fixed in the EL version the Data Access Block then yippie!
Sure, I am the editor for ONDotnet.com, but I really like this interview. The emphasis is trying to explain to the Linux developer why Mono/CLR development is the way to go. I am in!
I've spent most of the last week in Redmond seeing some new stuff and meeting up with old friends. While I was here I scheduled some time to sit down with Steve Lasker of the Visual Basic/Visual Studio Team. His team in in charge of the Typed DataSet in Whidbey.
I met with him to discuss the inheritability of Typed DataSets for business logic. If you've been reading much of what I have written in the last three years, you probably know how long I've advocated the use of Typed DataSets as a replacement for Business Objects. Alas, I've finally been convinced by Steve that they never intended Typed DataSets to be inherited.
In our discussion, he suggested using Typed DataSets and registering for events to do simple business logic is where they envisioned to be the limit of that use. They seem to be convinced that the DataSet can be too heavy for certain situations. They've spent a lot of time in the Whidbey bits to make object binding work much better than in the 1.x Framework.