Enterprise Library evolved from the original Application Blocks; unification because blocks were less compatible with each other than desirable. Unity block is new for Dependency Injection in EL4.

Okay... good overview so far. Hope this leads to some concrete examples, because I haven't worked with EL before. I really want to find out if it's worth using over something more agile like NInject.

Okay, Unity debugging apparently not very easy because of complexity. I think that (calling it out explicitly) kinda answers my question on NInject then. I can see in his sample that the stack traces have been simplified, but it still looked quite a bit more intimidating than I had expected... then again, it is probably on par with NInject at this point.

Bit surprised that message formatting was the slowest part of their logging framework. Bit bemused that they are using log4net as a comparison point, since log4net is far from fast (even though its authors are pretty impressed with the performance of their own code).

What is with the recurring Star Trek theme and jokes? ... Nevermind... database sample app now; starship maintenance (or Starfish maintenance if you mispronounce it).

Fluent interfaces apparently starting to become a thing too. Seems like MS will eventually get 'there' too, but a bit afraid that it all is going to be a lot heavier than it needs to be. Still... it looks good from what is shown.

EL apparently allows use of a different injection framework as well, so it is possible to use NInject with the rest of the library. EL 5.0 also vastly simplified internally and at the API.

Configuration looks pretty hideous, but apparently this is something being worked on to make it easier. Showing some samples of the current thinking now. Wizards with tasks that create multi-block configurations.

Interesting picture... graph-like-view to visualise dependencies, can show injection paths. App-config graphical view looks interesting... higher level view on existing config?

Details on entlib.codeplex.com