Summary

In this chapter you looked at the functionality of a VSTO Outlook add-in and learned why VSTO add-ins are preferred over shared add-ins. The main reason is that VSTO loads add-ins into separate application domains, thereby reducing the possibility that a problematic add-in will adversely affect other VSTO add-ins. VSTO also addresses the shutdown problem that occurs with managed shared add-ins that implement the IExtensibility2 interface. You also learned about the new architecture of VSTO Outlook add-ins when you install VSTO 2005 SE. Next, you looked at the basic objects in the Outlook object model hierarchy, and then you learned how to create menus and menu items in the main Outlook window.

We also looked at how you can debug an Outlook add-in, and you learned how to set environmental variables that let you display errors in a message box or write them to a log file. You also saw how you can reenable add-ins that have been soft-disabled or hard-disabled. Finally, we looked at the Outlook object model guard, and you discovered how you can avoid displaying the security warning when you access restricted properties and methods.

0 0

Post a comment