Before I get into the post, let me start off with a word of
advice for new bloggers. Never say in a post, this is the first
of many to come. RESIST! You are just setting yourself up for
never doing that second post. I know as the last post in this
series was five months ago. ;-)  In the last post, I introduced
the concept of ExportProviders as a way to customize how the
CompositionContainer discovers exports. One of the primary use
cases for doing this is to provide default exports, which is
particularly important for cases where you are importing a
single value for which there are multiple present. The common
case I like to use is the overused Logger example. Let’s say you
have multiple loggers in the system, which are used for
different functions. One logger logs locally, while others can
log remotely perhaps invoking a web service, or using MSMQ.
These loggers are all pluggable, as different organizations that
use the app may have different needs. Each of these loggers
export an ILogger contract.  Now most