Office development
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

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

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.

If you are developing a managed add-in by using Microsoft Visual Studio 2005 Tools for the 2007 Microsoft Office System Second Edition, always use the Application object that is provided by Visual Studio 2005 Tools for Office SE. Unless you intend to automate a new instance of Outlook, do not use the New or new keyword to create a new instance of Outlook, as this instance of the Application object is not trusted from the perspective of the Outlook Object Model Guard. If your add-in uses an untrusted instance of the Application object, depending on the version of Outlook that the client is running, the add-in by default will invoke Outlook's Object Model Guard on a number of members of the object model. For more information about the behavior of the Object Model Guard in Microsoft Office Outlook 2007, see Code Security Changes in Outlook 2007. Note that even though the Code Security Changes in Outlook 2007 article refers to COM add-ins that are trusted by default, this trust applies to managed add-ins the same way. Regardless of whether the add-in is managed or not, the trust is based on the assumption that the add-in uses a trusted Application object.

© 2016 Microsoft