My concern with that is down the road if we end up using references to other objects and they are 15.0 e.g. Microsoft Excel 15.0 Object, Word, etc. Then we're going to need to make sure that we point the reference to the Office 14 folder each time. ProjectMicrosoft Excel 12.0 Object Library reference upload. Chamdan 15.0 object library dll download, microsoft word 15.0 object library download, one of On the Assemblies page, select Microsoft.Office.Interop.Word in the Component Name list, and then hold down the CTRL key and select Microsoft.Office.Interop.Excel. Find answers to MSAccess MISSING: Microsoft Outlook 15.0 Object Library from the expert community at Experts Exchange.

-->

To use the features of a Microsoft Office application from an Office project, you must use the primary interop assembly (PIA) for the application. The PIA enables managed code to interact with a Microsoft Office application's COM-based object model.

Microsoft Outlook 15.0 Object Library Missing

Note

Interested in developing solutions that extend the Office experience across multiple platforms? Check out the new Office Add-ins model. Office Add-ins have a small footprint compared to VSTO Add-ins and solutions, and you can build them by using almost any web programming technology, such as HTML5, JavaScript, CSS3, and XML.

When you create a new Office project, Visual Studio adds references to the PIAs that are required to build the project. In some scenarios, you might need to add references to additional PIAs (for example, if you want to use a feature of Microsoft Office Word in a project for Microsoft Office Excel).

This topic describes the following aspects of using the Microsoft Office PIAs in Office projects:

For more information about primary interop assemblies, see Primary interop assemblies.

Separate primary interop assemblies to build and run projects

Visual Studio uses different sets of the PIAs on the development computer. These different sets of assemblies are in the following locations:

A folder in the program files directory
These copies of the assemblies are used when you write code and build projects. Visual Studio installs these assemblies automatically.
The global assembly cache
These copies of the assemblies are used during some development tasks, such as when you run or debug projects. Visual Studio does not install and register these assemblies; you must do this yourself.

Primary interop assemblies in the program files directory

When you install Visual Studio, the PIAs are automatically installed to a location in the file system, outside of the global assembly cache. When you create a new project, Visual Studio automatically adds references to these copies of the PIAs to your project. Visual Studio uses these copies of the PIAs, instead of the assemblies in the global assembly cache, to resolve type references when you develop and build your project.

These copies of the PIAs help Visual Studio avoid several development issues that can occur when different versions of the PIAs are registered in the global assembly cache.

Starting with Visual Studio 2017, these copies of the PIAs are installed to following shared locations on the development computer:

%ProgramFiles%Microsoft Visual StudioSharedVisual Studio Tools for OfficePIA
(or %ProgramFiles(x86)%Microsoft Visual StudioSharedVisual Studio Tools for OfficePIA on 64-bit operating systems)

Note

For older versions of Visual Studio, these PIAs will be installed to the Visual Studio Tools for OfficePIA folder under the %ProgramFiles% folder for that version of Visual Studio.For Example: %ProgramFiles(x86)%Microsoft Visual Studio 14.0Visual Studio Tools for OfficePIA

Primary interop assemblies in the global assembly cache

To perform certain development tasks, the PIAs must be installed and registered in the global assembly cache on the development computer. Typically, the PIAs are installed automatically when you install Office on the development computer. For more information, see Configure a computer to develop Office solutions.

The Office PIAs are not required on end-user computers to run Office solutions. For more information, see Design and create Office solutions.

Use features of multiple Microsoft Office applications in a single project

Every Office project template in Visual Studio is designed to work with a single Microsoft Office application. To use features in multiple Microsoft Office applications, or to use features in an application or component that does not have a project in Visual Studio, you must add a reference to the required PIAs.

In most cases, you should add references to the PIAs that are installed by Visual Studio under the %ProgramFiles(x86)%Microsoft Visual StudioSharedVisual Studio Tools for OfficePIA directory. These versions of the assemblies appear on the Framework tab of the Reference Manager dialog box. For more information, see How to: Target Office applications through primary interop assemblies.

If you have installed and registered the PIAs in the global assembly cache, these versions of the assemblies appear on the COM tab of the Reference Manager dialog box. You should avoid adding references to these versions of the assemblies, because there are some development issues that can occur when you use them. For example, if you have registered different versions of the PIAs in the global assembly cache, your project will automatically bind to the version of the assembly that was registered last—even if you specify a different version of the assembly on the COM tab of the Reference Manager dialog box.

Note

Some assemblies are added to a project automatically when an assembly that references them is added. For example, references to the Office.dll and Microsoft.Vbe.Interop.dll assemblies are added automatically when you add a reference to the Word, Excel, Outlook, Microsoft Forms, or Graph assemblies.

Primary interop assemblies for Microsoft Office applications

The following table lists the primary interop assemblies that are available for Office 2016, Office 2013 and Office 2010.

Microsoft Outlook Object Library Download

Office application or component	Primary interop assembly name
Microsoft Access 14.0 Object Library Microsoft Access 15.0 Object Library	Microsoft.Office.Interop.Access.dll
Microsoft Office 14.0 Access Database Engine Object Library Microsoft Office 15.0 Access Database Engine Object Library	Microsoft.Office.Interop.Access.Dao.dll
Microsoft Excel 14.0 Object Library Microsoft Excel 15.0 Object Library	Microsoft.Office.Interop.Excel.dll
Microsoft Graph 14.0 Object Library (used by PowerPoint, Access, and Word for graphs) Microsoft Graph 15.0 Object Library	Microsoft.Office.Interop.Graph.dll
Microsoft InfoPath 2.0 Type Library (for InfoPath 2007 only)	Microsoft.Office.Interop.InfoPath.dll
Microsoft InfoPath XML Interop Assembly (for InfoPath 2007 only)	Microsoft.Office.Interop.InfoPath.Xml.dll
Microsoft Office 14.0 Object Library (Office shared functionality) Microsoft Office 15.0 Object Library (Office shared functionality)	office.dll
Microsoft Office Outlook View Control (can be used in Web pages and applications to access your Inbox)	Microsoft.Office.Interop.OutlookViewCtl.dll
Microsoft Outlook 14.0 Object Library Microsoft Outlook 15.0 Object Library	Microsoft.Office.Interop.Outlook.dll
Microsoft PowerPoint 14.0 Object Library Microsoft PowerPoint 15.0 Object Library	Microsoft.Office.Interop.PowerPoint.dll
Microsoft Project 14.0 Object Library Microsoft Project 15.0 Object Library	Microsoft.Office.Interop.MSProject.dll
Microsoft Publisher 14.0 Object Library Microsoft Publisher 15.0 Object Library	Microsoft.Office.Interop.Publisher.dll
Microsoft SharePoint Designer 14.0 Web Object Reference Library	Microsoft.Office.Inte

Microsoft Outlook 15.0 Object Library Missing