Continuing from yesterday, I was testing how hard it is to work with two domains, I found this and it seemed like a good starting place. I started moving things around to understand how it all fits together, and soon I started getting remoting errors… it made me think, I really don’t want remoting problems to be a normal type of problems you get when of developing plugins, however is not a dead option just yet.
When using external dependencies in a composed application you can get a ComposablePartException temporarily I added the dependency to the main project but I am hoping there is a better way to tell MEF about external dependencies that should be “brought in with a type”.
BTW if you are playing with debugging capabilities and related, make sure you have the option “Just my code” in options not selected. If messing with appdomains check that the option for debugging other appDomains is enabled.
Next I am actually trying to integrate this into the project (i.e. where I want this to work) and see what breaks
The convention based stuff in MEF is truly simple. You use a RegistrationBuilder to set what types we are interested in, in my case I wanted to get all types derived from an interface, but I tested with a base class and it worked too, when you are doing that you can create a part builder (as below) and this is where you can set the creation policy which helps when you need to set whether there is one shared instance between many imports or you create one per each importer.
When you want to get the exports you can use a DirectoryCatalog like this
if you want to get the exported types you get a container and compose it
ok, so I hit the dependencies problem, need to read more about this.