It used to be that if you wanted to track a message through various Object Model events such as NewInspector and ItemSend , one way to do it was to grab PR_SEARCH_KEY . A customer recently discovered that this doesn’t always work after applying a recent hotfix. Before applying the hotfix, PR_SEARCH_KEY would remain unchanged during the various events. After applying the hotfix, if they were in cached mode they would see the search key change during the send event, but only if the user saved the message,

I have been working lately with this customer who was trying to create new signature files under %APPDATA%\Microsoft\Signatures folder which will be used by Outlook 2007 (SP2) but what we discovered is that whenever they try to use it, it used to crash Outlook. This was the content of the HTML Signature file that we were using. < HTML > < BODY > < IMG SRC ="http://www.server.com/logo.jpg" /> </ BODY > </ HTML > .csharpcode, .csharpcode pre { font-size: small;

Let’s have fun with the object model and search folders: Outlook running a profile in online mode. Create this macro: Sub TestAdvancedSearchComplete()     Dim sch As Outlook.Search     set sch = Application.AdvancedSearch("Inbox", "urn:schemas-microsoft-com:office:office#Keywords like 'Test'", True, "MySearchFolder")     sch.Save ("MySearchFolder") End Sub Run the macro, observe the folder. On the same machine, create

Ryan posted an article about some changes we're making in Outlook 2007 SP2. The gist is we're changing Outlook's shutdown behavior to always shutdown regardless of whether there are other running applications using the Outlook Object Model. He's looking for feedback on the logic change, so be sure to send him your comments.

Are you having hard time in adding WinHTTP.dll into Outlook 2007 VBA references on your Vista machine, so let me tell you that we are aware of it. The problem is shown below.. Look at the location part, which is for sure invalid path. The root cause is the installation of this DLL into the registry. Windows XP registry: HKEY_CLASSES_ROOT\TypeLib\{662901FC-6951-4854-9EB2-D9A2570F2B2E}\5.1\0\win32: C:\WINDOWS \System32\winhttp.dll Vista registry: HKEY_CLASSES_ROOT\TypeLib\{662901FC-6951-4854-9EB2-D9A2570F2B2E}\5.1\0\win32:

I don't know why we see a lot of customers trying to automate Outlook from a service. It’s pretty well documented that it’s a bad idea. Outlook Object Model (OOM) was written for automating Outlook for a user sitting at the box running it. See, Outlook is very personal and I do mean, it’s very, very personal. Outlook and OOM are as much about being client side as any application with an associated API can be. They will throw-up dialogs for warnings and errors… they will ask you for input based-upon

You might have faced this issue if you have used Outlook to send emails to SMTP recipients (non-exchange). Whenever you attach any MSG file to attachments it gets converted to inline attachment for the recipients. It made my colleague Akash worried why its happening and I have to explain him Why. Here is the story... Outlook and Exchange both are responsible for content conversation on the basis of protocol being used. If it’s MAPI (Outlook connecting to Exchange), Outlook will not touch the

When you use OOM under .NET, your using managed code around COM objects via the Outlook Primary Interop Assembly (PIA). When you have managed code working with COM in this way, you have to be very careful to clean-up your references. .NET will hold onto COM objects, sometimes causing leaks, and sometimes reusing them (called COM Ressurection). This leaks… void onEvent_ItemSend( object Item, ref bool Cancel ) { try { MessageBox.Show( "Application ItemSend Event Fired." , "onEvent_ItemSend" ); } catch

How to display a message in an outlook window using the store id and item id using OOM. CDO 1.21 cannot just display a message without having it being in a state of forward, reply, etc - so OOM is a better solution. 'TODO - set a reference to the outlook object model ' Call DisplayMessage, passing the store ID and the sMessageID properties. ' Private Sub DisplayMessage(sStoreID As String, sMessageID As String) ' Create Outlook application. Dim oApp As Outlook.Application Set oApp = New Outlook.Application

Excellent news! We just published the Microsoft Office Outlook 2007 Auxiliary Reference: http://msdn2.microsoft.com/en-us/library/bb905149.aspx (This is a greatly enhanced version of the earlier Microsoft Office Outlook 2003 Integration API ) This reference was a huge collaborative effort, of which I was only a small part. Parts of this reference are based on my blog entries, but large sections of it were written by others. For instance, we have a new sample address book provider , written by Xiaoming