I agree with Peter on the bloat factor. I've personally never needed to use the DAAB or LAB because they're only practical at enterprise level and most mature software development enterprises already have their customized DataAccess/Logging frameworks in-place.
That said, the DAAB and LAB prove incomparable for an enterprise that is starting development on their own components so that they can learn the generic way to do it and then reduce the customizability and flexibility thereby completely avoiding the bloat in their own DataAccess/Logging frameworks. On Oct 13, 11:33 pm, Peter Smith <[email protected]> wrote: > On Mon, Oct 12, 2009 at 10:13 AM, Andrew Badera <[email protected]> wrote: > > > Finally, use something like the Enterprise Library Exception Handling > > Application Block (EHAB) and Logging Application Block (LAB) to give > > you configuration-driven control over your exception handling. Using > > "exception policies" you can configure the app to log and throw the > > exception during development, then flip the switch to log and sink the > > exception in production. > > > (Peter, they may be bloated, but they get the job done. Suggest > > alternatives if you will.) > > I almost instinctively (well, okay, trained in by my High School Latin > teacher after 4 years of it) jumped on the use of a plural form of > alternative, but in this case, it's proper, as there's a possible > alternative for each Microbloated choice. :) > > And bravo, Andy...your training is almost complete. Now if you'll just > anticipate my choices for avoiding bloat, I won't need to post at all! :) > > But actually, I liked the way the blocks worked when I was introducted to > them in a former .NET environment. Apache's log4net project is a good > alternative, but certainly requires a lot more care to get the results you > want. > > And the OP is already going the way of the custom class to present his > "magic strings", so, I'll not dust off THAT soapbox, except to say that "Any > string in quotes that you have to type more than once should be a constant > or a resource"....within reason. :) > > using <<const string LEFT_PARENS="(";>> gets a little annoying after a > while. :)
