So, EntLib 2.0 is available for download. It boasts jiggy-ness with the 2.0 Framework.
Back in the day, when EntLib was just a collection of Application Blocks, it pwned. I used the DAAB quite a bit - and loved it. The thing was almost perfect.
Then Application Blocks somehow became Enterprise Libraries. Only, it wasn't a marketing ploy - the libararies actually went full-blown mediaeval. And the Data Access stuff just got absurdly loopy/stupid - with all sorts of support for agnostic RDBMS accesss. In my mind, it was just too bulky to really be worth it.
And what was with all the configuration crap? I didn't give it much attention - I just remember installing EntLib seeing all sorts of crap about configuring this, that, and the other thing, and then looked at what they'd done to pooch the object model of the data access goodies and left the entire ball of wax for a future date. Only, that future date never arrived.
Strange thing is, I've talked with a number of people who've had about the same experience.
So, given that Enterprises will typically re-invent the wheel themselves (i.e. write their own libraries out of fear of 'Not Invented Here' causing them issues), does anyone really use EntLib? Am I just being a baby? Is it a pain in the butt, or is it pretty easy?
Would a bunch of simple to use assemblies be an even better approach than trying to pimp these libraries out for 'Enterprises'?
Oh you just picked my scab. This one just drives me out of my mind. How stupid is MS to completely RUIN the beauty of the app blocks by "enterprising" them to the point where no one but the most devoted koolaid drinker can use them. This is one of the most mind numbing developer-oriented hatchet jobs they've done (right up there with 347 diff licenses for VS).
BTW - all the "configuration" crap you're carping about is because now, the previously beautiful DAAB is DEPENDENT on the stupid config block. How completely SCREWED up is that? It goes deeper than that, I didn't get any further before I burned the old DAAB to a CD and put it in a safety deposit box. At least we have that. And honestly, the config block is the spawn of the devil too. How can they possibly bring such a complex and debauched solution to such a simple need. I hate them for this move.
Posted by: Carson McComas | January 20, 2006 at 03:06 PM
I just ran into this issue the other day. A small app I am reviewing with my company has hand-crafted data access code, and I think WTF, where is SqlHelper.vb (or .cs if your prefer)?
I had looked at EntLib 1.0 when if first came out and my reaction was also what happened to the DAAB? I hadn't looked back since. So I Googled this time to see what was up with EntLib, downloaded the bits, and thought my eyes were going to bleed revisting the complexity. I found the old DAAB downlaod and plugged that into the project. Fit like a glove, replaced all the data access code with DAAB calls in day or so, trimmed hundreds of lines out.
Posted by: Dave Murdock | January 23, 2006 at 10:32 AM