The core foundation of the Managed Add-In Framework is a “Contract”. Contracts are non-versioning interfaces that define the protocol for communicating across the boundary between to the host and the add-in. In order for these contracts to be valuable...

One of the key benefits of our new managed add-in model is the architecture our system uses to connect the host to the add-in. Our system defines something we call the Add-In Communication Pipeline that defines a series of abstractions that allow hosts...

The second of two articles we wrote for MSDN magazine was published online today (and available in news stands now): http://msdn.microsoft.com/msdnmag/issues/07/03/CLRInsideOut/default.aspx This article discusses the System AddIn pipeline and we promised...

Details about the System.AddIn’s Implementation of Add-In Discovery Last time we discussed several common approaches to add-in discovery and some of the pros and cons of each. We reviewed type hierarchy, custom attribute, and xml manifest based...