In the Publish Form As dialog box, when you type a name in the Display name field, you will notice that the Form name field reflects the display name by default. You can leave the form name to be the same as the display name or you can change the form name. The display name will be the caption at the top of your form. The display name will also be used to construct the name under which your form will be published. When you publish your form, the display name will be listed in the Choose Form dialog

In Outlook, custom forms are typically published to a forms library so that only one copy of a form is stored on your computer. Individual items contain a Message Class field that indicates which form to use to display the data that is contained in the item. When you publish custom forms to a forms library, Microsoft Exchange Server-based computers and Outlook use considerably less resources and bandwidth because the form itself does not need to be stored within each individual item. Considerations

One of my customer had created an Outlook Add-in using VSTO & Outlook Object Model (OOM). As per the business logic, he need to implement the WebViewURL in it. The MAPIFolder.WebViewURL works fine and take’s us to set value to it most of the times, but it doesn’t function as expected in some time; the strange thing is it’s not throwing any error or exception when we execute the code. //[Code Snippet : C# , VSTO, Outlook Object Model (OOM)] ... //Provide the non-default store path String pstPath

One of my customer reported that they have a store event sink, which is used to modify the stream of incoming messages in Exchange Server environment (2003). But their attachments are missing when they open & view the message in Microsoft Outlook or in Microsoft Outlook Web Access (OWA); But contrarily when we view the message in Microsoft Outlook Express or by using Collaboration Data Objects (CDO), we can open and view the attachments in the message. When we investigated regarding the issue,

Category: (100) Event ID: 1000 Date: Date Time: Time User: N/A Computer: Computer_Name Description

The code sample uses the RuleAction and RuleCondition objects to specify a rule that moves messages from a specific sender to a specific folder, unless the message contains certain terms in the subject. Note that the code sample assumes that there already exists a folder named "Outlook" under the Inbox. Code snippet: 1: Sub CreateRule() 2: Dim colRules As Outlook.Rules 3: Dim oRule As Outlook.Rule 4: Dim colRuleActions As Outlook.RuleActions 5: Dim oMoveRuleAction As Outlook.MoveOrCopyRuleAction

Whenever we work with Outlook 2007 UI, we click either "Send/Receive button" or press "F9" to send and receive emails. In couple of our cases we use to do programmatically you can make use of Outlook Object Model's (OOM) SendAndReceive method. You need to know that calling the SendAndReceive method is synchronous only. Syntax: expression .SendAndReceive( showProgressDialog ) Here, showProgressDialog - Indicates whether the Outlook Send/Receive Progress dialog box should be displayed, regardless of

Please view this wonderful Screencast from channel9, which easily we can able to create our own menu option to the context menu in Outlook. Per jwiese "...would you like to add your own menu option to the context menu in Outlook?  How about turning an email into a new meeting request without having to type in all the attendees or the body and subject?  Well, in this Screencast I'll show you how to add to the context menu and generate a meeting request that includes the email's recipients,

Exchange Server 2003 and later versions of Exchange Server provide support for certain Outlook features, and Office Outlook 2007 works better with Exchange Server 2003 or later in several ways for other features. Several of these features were introduced in Outlook 2003—most notably for synchronization processing, user synchronization status reports, and junk e-mail filtering. Instant Search and automatic Exchange server discoverability are new in Office Outlook 2007. Synchronization between Outlook

There are quite number of tools available to find the issues with Exchange Server environment. Here we’re going to view about “Event Viewer”. Interestingly Event viewer is it’s not directly meant nor designed for Exchange server, its designed for Windows OS environment. So what can we get in the Event viewer? Using the event logs in Event Viewer, we can gather information about hardware, software, and system problems, and you can monitor Windows operating system security events. In Event Viewer,