To use the features of a Microsoft Office application from an Office project, you must use the primary interop assembly PIA for the application. Interested in developing solutions that extend the Office experience across multiple platforms? Check out the new Office Add-ins model. 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, microsoft office 2010 primary interop assemblies free download you want to use a feature of Microsoft Office Word in a project for Microsoft Office Excel. Separate primary interop assemblies to build and run projects. Use features of multiple Microsoft Office applications in a single project. Full list of primary interop assemblies for Microsoft Office applications.
For more information about primary interop assemblies, see Primary interop assemblies. Visual Studio uses different sets of the PIAs on the development computer. These different sets of assemblies are in the following locations:. These copies of the assemblies are used when you write code and build projects.
Visual Studio installs these assemblies automatically. 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. 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 microsoft office 2010 primary interop assemblies free download 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 microsoft office 2010 primary interop assemblies free download assembly cache.
Starting with Visual Studiothese copies of the PIAs are installed to following shared locations on the development computer:. 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. For more information, see Design and create Office solutions. 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.
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. Some assemblies are added to a project automatically when an assembly that references them is added. For example, references to the Office.
The following table lists the primary interop assemblies that are available for OfficeOffice and Office When you install and register the Office PIAs in the global assembly cache either with Office or by installing the redistributable package for the PIAsthe 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 assembly runs on a computer that has the Office version of the same primary interop assembly, the binding redirect assembly instructs the.
NET Framework runtime to load the Office version of the primary interop assembly. For more information, see How to: Enable and disable automatic binding redirection. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. Skip to main content. Contents Exit focus mode. Note Interested in developing solutions that extend the Office experience across microsoft office 2010 primary interop assemblies free download platforms?
Note Some assemblies are added to a project automatically when an assembly that references them is added. Is this page helpful? Yes No. Any additional feedback? Microsoft office 2010 primary interop assemblies free download Submit. Submit and view feedback for This product This page. View all page feedback. Microsoft Office Microsoft Graph Microsoft Smart Tags 2. Microsoft Visio
