<?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>Mind the (ECE) Gap</title><link>http://blogs.msdn.com/b/stephen_griffin/archive/2012/03/01/mind-the-ece-gap.aspx</link><description>We’ve added a couple new C++ only events to Outlook 2010 which I have been asked to document. These events were added per customer request to help fill some gaps in the transition from ECE to Com Add-In. One of the events is available as of the October</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Mind the (ECE) Gap</title><link>http://blogs.msdn.com/b/stephen_griffin/archive/2012/03/01/mind-the-ece-gap.aspx#10276541</link><pubDate>Fri, 02 Mar 2012 16:07:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10276541</guid><dc:creator>Lev</dc:creator><description>&lt;p&gt;While this is certainly a step in the right direction, parity with OnSubmit/OnSubmitComplete is still sorely missing. &amp;nbsp;It&amp;#39;s not nice to make us go through every single item type when dealing with sending an item ( because there is a huge difference between OOM item behavior in Item.Send- see what you get in MeetingRequest in Item.Send ) when OnSubmit/OnSubmitComplete just hands us IMsg object that we can deal with uniformly.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10276541" width="1" height="1"&gt;</description></item></channel></rss>