Ryan has a new post up about changes we’re making to Outlook 2010 to make shutdown faster . These changes are building on the previous changes we made introducing Fast Shutdown. Two key takeaways: MAPI Providers now get Fast Shutdown by default. They may still opt out of Fast Shutdown by implementing IMAPIClientShutdown . Outlook 2010 will not call the OnBeginShutdown or OnDisconnection of addins during shutdown. Ryan gives plenty of best practices for rewriting your addins to deal with these changes

I’ve updated the Outlook MAPI Samples and posted a new project up on Codeplex: Outlook 2010 MAPI Samples . We’ll get the MSDN updated to point at these samples soon. The goal of this update, of course, was to get these samples working with Outlook 2010, especially in 64 bit mode. Most of the changes were minor, swapping ULONG for ULONG_PTR, etc., but  I did have to make a couple big changes: None of the samples link to mapi32.lib anymore. I talked about this already. This was actually easier

I’m repeating myself – I did use a variation on this title before. In this case, suppose you’re using a custom transport provider, like MrXP , and you’re delivering to a regular (not wrapped) PST. In Outlook 2003, this worked great. If you had rules set up, they all got fired on delivery. In Outlook 2007 though, this stopped working. The basic design of a transport provider is this: 1 - Outlook's protocol handler has a function which will get messages from the transport. 2 - The transport provider

I previously wrote about some changes the development team had in mind for Outlook 2007 SP2 in the area of shutdown. The change discussed there, known as Shutdown With External References, allows Outlook to shut down completely even if there are outstanding Object Model references. The second major improvement in shutdown is known as Fast Shutdown, which allows a MAPI client such as Outlook to signal to the providers that a shutdown is imminent. As we get nearer to SP2, I’ve been asked to provide

The first answer I give to customers asking for tips on making their store provider work with the latest versions of Outlook is "be well behaved". I've had a couple message store provider cases recently that illustrate this and give me an opportunity to expand on that statement and give some concrete guidance. The case of the missing search folders The customer's message store wasn't working well in Outlook 2007. Outlook would recreate it's persisted search folders every time it booted.

When I announced the Outlook 2007 Auxiliary Reference , I noted there were a few issues with the wrapped PST sample that I hadn't had time to fix. Well, they're fixed now. You can find the updated download here: http://www.microsoft.com/downloads/details.aspx?FamilyID=ee0af8fd-bbb7-44de-be4d-f33cb1b59563&displaylang=en It should say Nov07 for version. If it says Oct07, then the new version hasn't propagated to all the servers yet. It should update soon. BTW - while I was working on the last MFCMAPI

[This is now documented here: http://msdn2.microsoft.com/en-us/library/bb905130.aspx ] There are a few places in Outlook that need to enumerate the folders in the message stores in a profile. It's usually looking for folders of a certain type. Normally this isn't a problem, but for some message stores this can be a big deal. Consider the Public Folder store. It will typically have thousands of folders, which may be scattered on servers around the world. Crawling through and opening every public folder

I managed to waste half a morning figuring out something I'm supposed to already know. Dev asked if I could confirm that MrXP works with Outlook 2007 so we can include it in some upcoming documentation. Sure thing. First step is to install it right? Here's the simple little script Jason and I were using to install MrXP: copy .\release\mrxp32.dll %windir%\system32 %windir%\system32\rundll32.exe %windir%\system32\mrxp32.dll MergeWithMAPISVC MergeWithMAPISVC was just an export that did all the file

We've gotten a rash of cases where message store developers complain that their store worked "perfectly fine" against Outlook 2003, but is broken now with Outlook 2007. The common symptom with all of them is that at some point, Outlook stops rendering any items in a folder. Maybe some times you can click on a folder and items will show up, but at some point, you get nothing. Once you get nothing, you continue to get nothing. Clicking on another folder and clicking back may or may not fix

[This is now documented here: http://msdn.microsoft.com/en-us/library/bb821096.aspx , http://msdn.microsoft.com/en-us/library/bb821097.aspx , http://msdn.microsoft.com/en-us/library/bb821099.aspx , http://msdn.microsoft.com/en-us/library/bb821100.aspx ] (Now that Outlook 2007 is available I'm reposting some of the articles from the Outlook 2007 Beta Documentation series. Some of the articles are virtually unchanged, others are completely different to reflect the differences between Beta and RTM.