Aug 26, 2009 at 4:47 PM

It would be fantastic to have an interface for CompositionContainer, much like there's an IUnityContainer interface for UnityContainer.

Thanks :)


Aug 26, 2009 at 5:00 PM

Hi Michael

Why do you need this? Is this for mocking the container?

Aug 26, 2009 at 5:04 PM

That's a good reason, yes.  Unfortunately, I'm afraid my reason is mostly aesthetic: dependencies look cooler when they are interfaces. :)

Aug 26, 2009 at 5:16 PM

Thanks Michael we will consider it. We do have a light abstract class that the container implements called ExportProvider. In general the places where one passes the container, they can use EP as long as long as you are not modifying the container (using batches). EP only supports retrieval methods.


Aug 30, 2009 at 1:13 AM

There are a handful of good reasons to wrap the export provider - this is one. It also lets you check assemblies from a directory and replace that silly GetExport, check, get value stuff with a simple GetItem method that is cleaner to use.

Doing it yourself is good and bad, it certainly increases the entropy in our already chaotic world .