May, 2008

Exchange Web Services Message cycle 

• When a client application requests information from the Exchange store, an XML request message that complies with the SOAP standard is created and sent to the Exchange server.
• When the Microsoft Exchange server receives the request, it verifies the credentials that are provided by the client and automatically parses the XML for the requested data.
• The server then builds a SOAP response that contains XML data that represents the requested strongly typed objects and their properties.
• The XML data is sent back to the client application in an HTTP response.
• The client application then deserializes the XML and uses the data to reform the strongly typed objects.

Welcome to Exchange Server Development Technologies - Series # 1  

In this series, we will discuss about the Exchange Rules. This topic provides information about using Exchange Rules to develop messaging applications. 

• Exchange rules are typically used to specify user-defined actions that are to be performed on messages that arrive in folders of the user's mailbox.
• In addition, it is possible to use a set of predefined rules on Public Folders 
• Exchange Server uses rules on mailboxes and other folders to automatically execute actions on objects in the folders.
• You can use rules to develop applications that carry out predefined or custom actions, even at times when the application is not running.
• Rules can be performed on the Exchange store (server-side) or on Microsoft Outlook (client-side, deferred action rules).

For more detailed information, please find this MSDN documentation.

In this series, we will learn "How to create Outlook Preview Handlers in Outlook 2007 ?".  First we'll know what is Preview Handlers and where it can be used, along with a downloadable sample.

What are Preview Handlers and where it's used?

Preview handlers are called when an item is selected to show a lightweight, rich, read-only preview of the file's contents in the view's reading pane. This is done without launching the file's associated application.

To know more about preview handler, please read more in this detailed MSDN article.

Preview Handler - Sample:

• Martijn Hoogendoorn inspired & created a Shockwave Flash preview handler and available in this wonderful article along with installer sample. Basically, it's just a plain UserControl which hosts the ActiveX wrapper for the player. It works from both Outlook 2007 and Windows Vista.

Welcome to Outlook Programming series  # 10

In this series, we will learn "How to customize Outlook 2007 (Office 2007) Ribbon functionality". I found these below given MSDN articles which describes how we can customize Office 2007 (including Outlook 2007) ribbon functionality.

• Customizing the 2007 Microsoft Office Fluent User Interface Using Visual Studio 2005 Tools for Office Second Edition (Part 1 of 2)
• Customizing the 2007 Microsoft Office Fluent User Interface Using Visual Studio 2005 Tools for Office Second Edition (Part 2 of 2)
• Customizing the 2007 Office Fluent Ribbon for Developers (Part 1 of 3)
• Customizing the 2007 Office Fluent Ribbon for Developers (Part 2 of 3)
• Customizing the 2007 Office Fluent Ribbon for Developers (Part 3 of 3)
• Custom Task Panes, the Office Fluent Ribbon, and Reusing VBA Code in the 2007 Office System
• Developer Overview of the User Interface for the 2007 Microsoft Office System.

Welcome to troubleshooting performance issues in MS Outlook Series - Part 1

Have you face any one of the following issues with Outlook 2007 ?

Whether do you think,

Do you know, why do you face these issues?

It might be a performace issue with respect to Outlook 2007. The performance issues may be caused by one or more of the following:

Please find this wonderful article, which talks how to troubleshoot the performance issues in Outlook 2007.

Welcome to Outlook Programming series  # 9

In this series, we will learn "How to systematically release the objects - Add-in's for Outlook 2003 & Outlook 2007 ?". I found this MSDN article which describes how all Outlook add-ins should systematically release their references to Outlook objects when they are no longer needed. Failing to systematically release reference to Outlook objects can prevent Microsoft Office Outlook 2003 & Outlook 2007 from shutting down properly.

For more information about this problem that affects managed add-ins written for Outlook 2003 using Visual Studio .NET, see KB 317109: Office application does not quit after automation from Visual Studio .NET client.

Please find Mstehle's blog: OOM.NET: Part 2 - Outlook Item Leaks (Outlook + OOM + .Net Issues), which describes in detail and has the resolution to solve the issue...

When you try to start Microsoft Office Outlook 2003, the program does not start. Additionally, you receive the following error message:

Do you know....this issue may occur if you install and then uninstall Microsoft Office Outlook 2007 Beta 2 on a computer that has Outlook 2003 installed. When you uninstall Outlook 2007 Beta 2 version, the Outlook 2007 Beta 2 version of the MSMapi32.dll file is not removed from the following folder on your computer:  "C:\Program Files\Common Files\System\Msmapi\LocaleID"

Please view this useful MSDN KB Article. It has the information about the issue, its cause, resolution for this issue

Welcome to Outlook Programming series  # 8

In this series, we will learn "How to update existing items in an Outlook folder to use a new custom form?". I found this MSDN article which describes programatically how to update existing items in an Outlook folder to use a new custom form? 

This article describes how to update items in an Outlook folder so that those items open using a different form than the form that the items are currently associated with.

When using a custom form containing a ListBox control, Outlook unexpectedly adds a new possible value to the control.

Do you know....this behavior is due to the storage limitation of Keywords fields. If the control is bound to a field of type Keywords and you select a number of possible values in the control, the field may exceed its 255-character maximum length. This causes the last value to be truncated. Because the custom Keywords field now contains a new value that is not one of the options in the control, Outlook adds this new value to the list of possible choices in the control.

Please view this useful MSDN KB Article. It has the information about the issue, its cause, re-solution for this issue

When you send an item that is based on a custom form, the form is not sent and you receive the following error message: "Operation Failed" 

This issue will happen if, a Recipient field on the custom form is configured with an initial value and with the Calculate this formula automatically option for that value.

Please view this useful MSDN KB Article. It has the information about the issue, its cause, workaround solution for this issue.