Are you using the Microsoft Enterprise Library? [closed]

Answer 1

Having worked on a number of med-large web projects I can recommend the caching block from ent library as it allows you to use nCache or similar with a simple config change. This allows the dev team to use TDD without the need for nCache (or similar) to be installed everywhere.

Log4Net is far superior to the ent lib logging block IMHO.

Security / Crytography blocks I have used a few times and generally find that they do what they say on the tin without being too onerous or complicated.

The rest of the framework is beaten hands down by other simpler and (IMHO) better solutions Data access - nHibernate, ActiveRecord, Tarantino

Unity - windsor, spring etc

Validation - I use the castle stack

Answer 2

I like using it, ESPECIALLY for small projects, because it's a "I don't care, this stuff simply works and provides everything I need without hassles".

Overengineered? How so?

Answer 3

I like the old Application Data Block that was separate from Enterprise Library. It's very simple and saves you a lot of time. We tried moving to the Enterprise block but it wasn't worth the heft.

We use log4Net for logging and that works ok.

Answer 4

We use it (specifically, Unity, Logging and Validation), and I can't say I'm a big fan of it.

The logging block is definitely over-engineered, and ironically still lacks a lot of flexibility. I was amazed at how much code I had to rip out and replace if I wanted to write more structured logging messages to a DB rather than just a single table with generic messages. The documentation is sketchy, and it's really hard to follow what actually happens in your logger.

Unity actually works ok though. Personally, I'd rather avoid DI containers entirely, but if you have to use one, Unity seems fine.

I haven't really been involved in the code that uses the Validation block, so I can't tell you how that works out.

But in general, I'd say that yes, it is overengineered, and unless it does exactly what you need out of the box, you're probably better off without it.

Answer 5

+1 for over-engineered. We use log4net instead of the logging or exception handling blocks. We use the native .NET System.Security namespace instead of entlib encryption blocks. Some of the tracing tools are nice, but we don't have anything in production that uses them.

Answer 6

Enterprise Library is an overkill. It is too complex and inflexible. So we don't use.

In our projects (including those that target distributed computation scenarios over Windows Azure) we use Lokad Shared Libraries as a lightweight replacement. It plugs to log4net for logging, Autofac IoC for configuration, provides custom business rules, validation and exception handling (with reliability) application blocks, while packing all the required assemblies in a few dll files.