Plugin Framework - can there be too many addin assemblies?

Posted by spooner on Stack Overflow See other posts from Stack Overflow or by spooner
Published on 2009-09-14T21:59:59Z Indexed on 2010/04/10 3:03 UTC
Read the original article Hit count: 393

Filed under:
|
|
|
|

Hi,

The product I'm working on needs to be built in such a way that we have a quote engine driven by a pluggable framework.

We are currently thinking of using MAF, so we can leverage separation of the host and addin interfaces for versioning.

However, I'm concerned that we'd have lots of assemblies, it's likely that we'd have one for each quote engine addin - of which there could be 100 going forward, we also need to support multiple versions, so there could be lots of assemblies in total.

The quote engine also uses WF to drive it, which means each AppDomain for each addin will need a workflow runtime associated with it. This seems quite heavyweight, however we can unload unfrequently used addins.

Does this seem like a good design? We've also looked at a single AppDomain solution using an IOC container to load addin types, but I'm concerned that we won't be able to unload any of the assemblies, given their quantity.

© Stack Overflow or respective owner

Related posts about maf

Related posts about .NET