Changes to Dependencies When Using the Unity Application Block

Retired Content
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
The latest Enterprise Library information can be found at the Enterprise Library site.

The Unity Application Block provides a lightweight, extensible dependency injection container with support for constructor, property, and method call injection. You can use the Unity Application Block or its dependency injection container mechanism in your own applications to create instances of Enterprise Library objects and instances of your own custom business objects and services that depend on other objects or services.

However, you do not have to do this. You can continue to create instances of objects using the same techniques as in earlier versions of Enterprise Library.

If you decide to use the Unity Application Block, this becomes an additional dependency for the other application blocks and your application. In addition, like all the other application blocks, the Unity Application Block has a dependency on ObjectBuilder.

For more information and schematic views of the dependencies between the Unity Application Block, the Enterprise Library core, and ObjectBuilder, see Dependency Schematics.