<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Brief Introduction to our Architecture for Managed Add-Ins [Jesse Kaplan]</title><link>http://blogs.msdn.com/clraddins/archive/2007/02/23/brief-introduction-to-our-architecture-for-managed-add-ins.aspx</link><description>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</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>QuickLinks: System.AddIn and the Microsoft AddInFramework</title><link>http://blogs.msdn.com/clraddins/archive/2007/02/23/brief-introduction-to-our-architecture-for-managed-add-ins.aspx#4644346</link><pubDate>Thu, 30 Aug 2007 14:31:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4644346</guid><dc:creator>Mike Taulty's Blog</dc:creator><description>&lt;p&gt;System.AddIn in Framework V3.5 is about building hosts that load plug-in Add-Ins with functionality around...&lt;/p&gt;
</description></item></channel></rss>