Addin's: "A rose by any other name would smell as sweet"
For several months we have used "MAF: Managed Addin Framework", to describe the WinFX System.AddIn libraries, as well as the surrounding collateral that makes this offering compelling for addressing a large class of issues. However, the use of "MAF", as a catch all term, has caused some level of confusion. The confusion is generally in the usage of the word, "Framework". As we know, the .Net framework is "THE" system framework for managed code and the usage of the word "framework" as part of "MAF" was never intended as a substitute, replacement, or competing term. In fact, you will see no reference to the "Managed Addin Framework" in our documentation for the very reason that confusing may result. It has been simpler for many of us to call the Managed Addin solution space and all that it encompasses "MAF". From here on out I will be more specific in my usage of "Addin" related posts. Dare I even use the term "Addin, Add-in, AddIn, Add-In…" ;-)
We have begun to describe the semantics of "Add-in's" and its pertinent design considerations in blog posts. The guidance for building version resilient, isolatable, dynamic .Net "components" will be as import as the core libraries supporting "Add-in's". Guidance may be obtained via the Visual Studio Extensibility forum, the VSTA help content, as well as past and future posts on the subject from TQ and myself.
Q: Why is the System Add-in collateral referred to as WinFX Add-in?
A: The confusion has been resolved. I will henceforth refer to this solution as System Add-in :-) See this post.