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 2011 Cumulative Update, and the other just shipped in the February 2012 Cumulative Update.
The two new events are:
If you’re familiar with writing Exchange Client Extensions and Com Add-Ins in C++, this is likely sufficient information to handle these events. If not, you might want to review some samples which demonstrate handling events from the IDispatch::Invoke function. For example, I found this add-in on codeproject which handles Application events. In that code, the CAppEventListener::Invoke function is where you would handle the BeforePrint event.
While this is certainly a step in the right direction, parity with OnSubmit/OnSubmitComplete is still sorely missing. It'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.