Developer Issues When Upgrading Solutions to Outlook 2010
This topic describes issues to consider before you upgrade existing solutions to Microsoft Outlook 2010.
Microsoft Office 2010 is available in both 32-bit and 64-bit versions. You do not need to recompile existing (32-bit) managed add-ins, if you expect the add-ins to continue to run only on computers with 32-bit Outlook installed. If you expect your add-in to run on computers installed with 64-bit Outlook, be sure that you have built or will rebuild the add-in using Microsoft Visual Studio Tools for the Microsoft Office system 3.0 Runtime, or Microsoft Office development tools in Microsoft Visual Studio 2010, with the Any CPU option selected for the target platform on the Build tab of the Project Properties dialog box. Add-ins built with such settings work for both 32-bit and 64-bit versions of Office 2010.
Command bars are deprecated in the inspector and explorer in Outlook 2010. Although your add-in code that customized command bars in an inspector or explorer might still work in Outlook 2010, those who use your solution might not easily find your custom commands because those commands appear on the Add-ins tab of the ribbon in the customized inspector or explorer. Instead of using command bars, use the IRibbonExtensibility interface in an Outlook add-in. For more information about using IRibbonExtensibility to customize the Outlook user interface programmatically, see the article Extending the User Interface in Outlook 2010.
Customizations to shortcut menus using events such as ItemContextMenuDisplay on the Application object might not operate as expected. These events operate on a CommandBar object that is returned in the event. Because command bars are deprecated in Outlook 2010, use IRibbonExtensibility to customize shortcut menus programmatically. For more information about customizing shortcut menus, see the article Extending the User Interface in Outlook 2010.