I think I can fix this if I can include the Microsoft.Vbe.Interop 14.0.0.0 in the project References of Visual Studio. But the only versionof Microsoft.Vbe.Interop I have on my development machine (same as machine which has Office 2010) is 12.0. All my software is up-to-date on this machine according to the web-update mechanism. The Microsoft Download Manager solves these potential problems. It gives you the ability to download multiple files at one time and download large files quickly and reliably. It also allows you to suspend active downloads and resume downloads that have failed. Microsoft Download Manager is free and available for download now. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. You should find the reference below, and possibly Microsoft Outlook 15.0 Object Library, if you need that. There are similar libraries for Word, Excel, etc.: Update: The Object Library should contain the Interop stuff. Try to add this to a source file, and see if it does not find what you need: using Microsoft.Office.Interop.Outlook. Could not load file or assembly 'office, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The DLL may have been in the Bin folder on your local machine for the Web program using IIS Express, but the DLL is not there in the Bin folder for the Web program on the test IIS server.

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.

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.

• Turbotax download 2000 for mac. 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:

Microsoft.vbe.interop.forms

• %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.

/free-previz-software.html. 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.

Binding redirect assemblies

When you install and register the Office PIAs in the global assembly cache (either with Office or by installing the redistributable package for the PIAs), the binding redirect assemblies are also installed only in the global assembly cache. These assemblies help make sure that the correct version of the primary interop assemblies is loaded at run time.

For example, when a solution that references a Office 2010 assembly runs on a computer that has the Office 2013 version of the same primary interop assembly, the binding redirect assembly instructs the .NET Framework runtime to load the Office 2013 version of the primary interop assembly.

For more information, see How to: Enable and disable automatic binding redirection.

See also

This the assembly necessary to do Office 2013 Excel interop

Dependencies

This package has no dependencies.

Used By

NuGet packages (43)

Showing the top 5 NuGet packages that depend on Microsoft.Office.Interop.Excel:

Microsoft Vbe Interop

Microsoft.vbe.interop Download

GitHub repositories (8)

Showing the top 5 popular GitHub repositories that depend on Microsoft.Office.Interop.Excel:

Microsoft.vbe.interop Version 15.0.0.0

Version History

Microsoft Vbe Interop 15.0 Download