Best Practices in Developing Managed Outlook Add-ins

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Even though the Outlook interop assemblies allow you to write managed solutions that interoperate with Outlook, Outlook predates the .NET Framework and is designed to support programmability through unmanaged languages such as Visual Basic for Applications (VBA) and Visual Basic. This topic lists the top areas that you should be aware of when you develop a managed add-in for Outlook.

• Systematically Releasing Objects

• Using a Separate Application Domain to Avoid Crashing

• Using a Trusted Application Object Provided by Visual Studio Tools for Office

• Scoping Variables Appropriately in Event Handlers

• Avoiding Unsupported Technologies in Managed Outlook Add-ins

• Using Late Binding If Depending on Multiple Versions of Outlook