.net - Own extensibility layer or MEF/MAF? -


For those who work with application extensibility in NAT, what do you prefer to do - your Extensibility Layer Creating or Using MEF (Managed Extensibility Framework) or MF (Management Add-in Framework)?

So far, I have used both methods of implementing application extensibility and I like the MEF for the fact that it makes it easier to load existing assemblies directly from the interface to a specific location For a implementation of (interface) for shortness of .NET)

What is the benefit of what you see in your specific detail layer priority? What are the disadvantages?

MEF has lots of advantages, whatever you have mentioned ... favorability, Modularity, lifelong management, and anything else I want to be available in the first class framework. It has been sent with the framework, so there is nothing to do and you know that it will be in compliance with the implementation.

It has been used in VS 2010 so that more commonly the real world example can not be found.

MF is not exactly the same thing, it is very specific for the system. AddIn and some other harsh requirements and satisfaction is the contract. After saying this, it specifically targets a specific type of extensibility that some people want.

I only go for a custom approach if I actually have very little footprint or an application that does not need all

of an additional overhead

Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -