- Install Primary Interop Assemblies and Visual Studio Runtime manually

Looking for:

Microsoft office primary interop assemblies 2010 free 

Click here to DOWNLOAD

     

Office primary interop assemblies - Visual Studio (Windows) | Microsoft Docs.

 

Upgrade to Microsoft Edge to take advantage microsoft office primary interop assemblies 2010 free the latest features, security updates, and technical support. 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. Separate primary interop assemblies to build and run projects. Use features of multiple Microsoft Office applications in a single project. Full list microsoft office primary interop assemblies 2010 free 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:. This set of the assemblies is used when you write code and build projects. Visual Studio installs these assemblies automatically. This set of the assemblies is used during some development tasks, such as when windows server r2 standard capacity free run or debug projects.

Visual Studio doesn't install and register these assemblies; you need to do it yourself. The PIAs are automatically added to a location in the file system, outside of the global assembly cache, while you install Visual Studio.

When you create a new project, Microsoft office primary interop assemblies 2010 free 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. When different versions of the PIAs are registered in the global assembly cache, you can face several development issues.

The added copies of PIAs will help you to avoid such issues. For Visual Studio and later, these 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 doesn't 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've 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. 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've registered different versions of microsoft office primary interop assemblies 2010 free PIAs in the global assembly cache, your project will automatically bind to нажмите чтобы перейти 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 microsoft office primary interop assemblies 2010 free redistributable package for the PIAsthe binding redirect assemblies are also installed only in the global assembly cache.

These assemblies ensure that the correct version of the primary interop microsoft office primary interop assemblies 2010 free is loaded at run time. For example, when a solution that references a Office electric 2.4 license key free 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. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.

Table of contents Exit focus mode. Table of contents. Note Interested in developing solutions that extend the Office experience across multiple platforms? Note Some assemblies are added to a project automatically when перейти на страницу assembly that references them is added.

Submit and view feedback for This product This page. View all page feedback. In this article. Microsoft Office Microsoft Microsoft office primary interop assemblies 2010 free Microsoft Smart Tags 2. Microsoft Visio