Bruce said:
Well, as I could understand for what I have read so far, DAB is not so
helpful, it might even get worse the overall performance .
There is a reflection hit for figuring out which data provider to use, but
other than that the performance is acceptable. But obviously, you can beat
it by writing straight ADO.NET. Using the EntLib DAAB, you should choose
carefully if you need some of the built-in features (perf counters, WMI,
database independence). If you need pure speed, you'll probably need
something more lightweight.
But what about the other blocks (criptography, security...) ? Have u
used any of them for real?
They work great, but again, if you need to analyze which of the features of
the EntLib you need. If you are already using DAAB, then using the Caching
Block fits right in. It's really a question of how much you want to "buy-in"
to using the EntLib.