MEF addict [Combining .NET 4’s type embedding and MEF to enable a smooth upgrade story for applications and their extensions]

This blog has moved to a new location and comments have been disabled.

All old posts, new posts, and comments can be found on The blog of

See you there!

Comments (2)
  1. realparadyne says:

    I recently had to deal with this issue for a server app that allows for plugins.  I didn't want to have a contract dll as I wanted to put the plugins in their own folders as well as avoid the versioning issues.  I didn't know about the type embedding so found a different solution using the DLR and c# dynamic references.  My MEF exports are typed by name strings and as 'object' rather than interface types and I can just call methods by name.  It seems to work very nicely that way too.

  2. David Anson says:


    Cool – that's a pretty slick alternative! Losing static type safety is a bit of a bummer, but it sure is a flexible solution. 🙂 Thanks for sharing!

Comments are closed.

Skip to main content