Restrictions on Contracts [Jack Gudenkauf]

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 for versioning they need to follow a set of constraints: at a high level they need…

8

Brief Introduction to our Architecture for Managed Add-Ins [Jesse Kaplan]

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 and add-ins to version independently and be completely unaware of how the…

1

2nd MSDN Magazine Article Hits the Web [Jack Gudenkauf]

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 to show the utilization of the model to enable compatibility as your Host and Add-In version independently. In this article we’ll first go into…

19

Behind the Scenes of Add-In Discovery in the Orcas System.AddIn [Jesse Kaplan]

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 discovery systems and primarily evaluated them on three high level criteria: development complexity, performance, and add-in developer…

7