<?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>Exposing Events From Non-VSTO Add-in Automation Objects</title><link>http://blogs.msdn.com/andreww/archive/2009/03/01/exposing-events-from-non-vsto-add-in-automation-objects.aspx</link><description>I posted a while back about exposing an automation object from an add-in that fires events . That post was couched in terms of VSTO add-ins. A customer asked recently how the same technique could be used in a non-VSTO add-in. So, that’s the topic of this</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Anith &amp;raquo; Exposing Events From Non-VSTO Add-in Automation Objects</title><link>http://blogs.msdn.com/andreww/archive/2009/03/01/exposing-events-from-non-vsto-add-in-automation-objects.aspx#9453645</link><pubDate>Mon, 02 Mar 2009 08:51:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9453645</guid><dc:creator>Anith &amp;raquo; Exposing Events From Non-VSTO Add-in Automation Objects</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.anith.com/?p=14523"&gt;http://www.anith.com/?p=14523&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>