Known issues in Outlook 2010 when you use the Outlook View Control


This article provides an overview of issues that can occur if you use the Outlook View Control as part of a custom solution that integrates with Microsoft Outlook 2010.

More Information

The Outlook View Control lets developers integrate Outlook views into custom programs and solutions. The Outlook View Control was primarily intended for use in folder home pages in Microsoft Office Outlook 2000. The Outlook View Control has continued to be included with Outlook in later versions, and this includes Outlook 2010.

Although restrictions were put on the control when it is used in a browser, the core functionality has stayed the same since 2001. For more information about the changes that were made in 2001, click the following article number to view the article in the Microsoft Knowledge Base:
311738 Developer information about the Outlook View Control security update
The following sections summarize issues that occur when you use the view control with Outlook 2010.

Outlook shutdown and instancing issues

In earlier versions of Outlook, instances of the view control would keep the Outlook process running. However, changes to Outlook shutdown behavior can adversely affect the view control. When a user exits Outlook 2010, Outlook now shuts down completely. In this scenario, the view control becomes nonfunctional because Outlook is no longer running. For more information about architectural changes that are related to how Outlook shuts down, visit the following Microsoft Developer Network (MSDN) website:Because of these changes, Microsoft only supports the view control when you use it on an Outlook folder home page or in a form that is displayed by an in-process Outlook add-in. This makes sure that Outlook is running and that the view control is not subject to other factors. These other factors may adversely affect the Outlook process from continuing to be available for the view control's use. Although you can use the view control on an external webpage or on a stand-alone (out-of-process) program, we do not recommend or support these scenarios. For example, Outlook may close unexpectedly, and this occurs if the user right-clicks a message in the view control.

Some problems that are related to the Outlook process may be avoided if Outlook is forced to start from an external program before the view control is rendered for the user. For example, you could automate Outlook and display an Outlook Explorer window to open Outlook before the view control is displayed or before a user interacts with the view control. However, because there are many variables and potential problems that are involved in scenarios such as these, we do not recommend this approach. Instead, we recommend that the view control is used only within Outlook. If you use the view control in any out-of-process scenario, Microsoft Customer Support cannot provide assistance, and hotfixes are not provided for these scenarios.

BUG #: 29202 (OfficeQFE)

The mouse does not work in Calendar view

If you set both the Folder and View properties to Calendar to display the Calendar view, the mouse does not function as expected. A fix for this issue is available in the Outlook 2010 hotfix package that is dated April 26, 2011. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2516474 Description of the Outlook 2010 hotfix package (outlook-x-none): April 26, 2011
Although this hotfix re-enables the shortcut menus, some shortcut menu commands are not available if the control is hosted in a location other than an Outlook folder home page. For example the Go to Date and Calendar Options commands are not available. There are no plans to correct this inconsistency. As a workaround, consider adding your own user interface to provide those commands. For example, the view control provides a GoToDate method so that you can programmatically change the date that is displayed in the control.

BUG #: 28154 (OfficeQFE)

SenderName and SentOnBehalfOfName properties no longer work with Outlook View Control Restriction

Both the SenderName and SentOnBehalfOfName properties refer to the From field in Outlook. If you use the Outlook View Control and either the SenderName or the SentOnBehalfOfName property together with the Restriction property, you receive an exception. The workaround is to use the Filter properties to search for items that are based on the From field. For example, you can use the following approach by using a Microsoft Visual Basic Scripting Edition (VBScript) script.

ViewCtl1.Filter = """urn:schemas:httpmail:fromname""" & " = 'John Smith'"
BUG #: 780207 (Office14)

View control causes a rendering issue when the parent container is resized

If you use the view control on a custom form or on a webpage in a browser, and the parent window is resized, the view control may prevent the parent window from re-drawing the screen correctly. This symptom has the same cause as the mouse that does not work in Calendar view, and the resolution is the same.

Keyboard shortcuts do not work in Calendar view

You cannot use the keyboard in Calendar view. We are investigating this issue and will update this article with more information as it becomes available. If you must have a fix for this issue, please contact Microsoft Customer Support.

BUG #: 840972 (Office14)

Selection object does not return items in Conversation view

If a view is set to Show as conversations, the Selection object of the Outlook View Control does not return selected items. This problem was corrected in the Outlook 2010 Cumulative Update. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2405793 Description of the Outlook 2010 hotfix package (outlook-x-none.msp): October 26, 2010

Folder paths may have to be updated after an upgrade to Outlook 2010

If you are using the view control to display a public folder, the folder path is no longer valid after you upgrade to Outlook 2010. The top-level folder for public folders was changed from "Public Folders" to "Public folders - <username>." This change was made to support having more than one public folder store that is loaded in a single MAPI profile. To update solutions so that they can work with Outlook 2010, you can retrieve the Session.CurrentUser object to build the path that has the user's name.

Note This is another scenario where, if you use the view control in a browser, this workaround becomes more difficult, and even unrealistic. This is because, typically, you cannot automate Outlook directly from a browser to retrieve the current user's display name.

View names may have to be updated after an upgrade to Outlook 2010

Some view names have changed in Outlook 2010. For example, what used to be called Day/Week/Month view is now called Calendar view in Outlook 2010. Make sure that your solution uses the correct view names in Outlook 2010.

Raksta ID: 2511230. Pēdējo reizi pārskatīts: 2011. gada 26. aug.. Pārskatījums: 1