A Case For and Against the Enterprise Library:
Already, I've run into an interesting issue: when it is better to forgo the code of the Enterprise Library and roll your own, vs. using existing code.
Roll your own what? Well, the MS Enterprise Library is a set of source code (in both VB.Net and C#) that provides an infrastructure for business applications. The "blocks" that are provided include: caching, configuration, data access and instrumentation, among others.
I know that many people have downloaded the application blocks. I don't know how many people are using them. I suspect far fewer.
I’ve spent a fair amount of time with the Enterprise Library…(codewise) it’s as complex as it is vast in what it attempts to accomplish. I’ve gotten the same reaction from many colleagues who insist it’s just simply too complex, and have the menality of (as mentioned in one of the comments): “My developer EGO is so big I think I can code better than you”. Don’t get me wrong, I like hammering out code as much as the next guy, but if there is something else out there that’s been tested (and in this case is free), why not have a look at it? I’ve worked with too many devs that have the above mentality…they are usually the type who could care less if they’re locked in a windowless room with an endless supply of caffeine and a computer…feed them specs and they churn out code. This is usually not the most cost effective way to go about it.
In the end, building applications is just like any other business…it’s all about the bottom line and shipping a quality product. Building software (at the enterprise level at least) is more about leveraging disperate systems and integration at this point than churning out new code. Yes there are plenty of edge cases that dictate otherwise…but I’d say at least 50% of the time what you’re looking for is already out there, either in commercial component you can buy, or in a reusable component already deployed on the LAN. Always have a look around to see what’s already out there…in the case of the Enterprise Library, the couple of hours it takes to ramp up on how to configure/integrate it is well worth the functionality it provides, plus it's quite extensible. Just don’t plan on memorizing the source overnight (or probably ever for that matter)…it’s incredibly complex. Cheers.
Share this post: 
|

|

|

|

|
