.net - MEF vs Mono.AddIn -
I am developing a .NET 3.5 C # desktop application. It should be extensible through plug-ins.
Are there any articles etc. Do I discuss differences between MEF and Mono.Adine to help me make informed decisions?
Or is it even better you have experience with these two structures and can comment on them?
Thanks, Patrick
[Note: I work on monodequal which Mono uses Eddie but I discussed the differences between MEF and Mono.
Writing code based on MEF, although the underlying remains are very flexible, on the contrary, Mono.Aidin is based on a tree of Metadata where the MAF team was discussed extensively with Glenn Block last week) You can plug your definition data / metadata / code into a rich schema, so extensions can add data / metadata as well as code.
MonoAdins gives you the Adsense management / packaging / repository / update system outside the box. For MEF, at this point, you have to build your own.
There is little hurdle for entry in the MEF, and much more design work has gone into its utility and underlying segregation. In addition, it is part of .NET 4, so it will be a big community of users who develop it for /.
At this point, if you have to plug into the data / metadata code and you want a ready packaging system, I recommend MonoAddin, otherwise I recommend the MEF going forward , It's likely that mono Edin's features will be implemented on MEF, so perhaps there will be a migration path towards MEF.
Comments
Post a Comment