Sep 07, 2010  The Microsoft Office 2010 Primary Interop Assemblies Bootstrapper Installer adds the option Microsoft Office 2010 Primary Interop Assemblies to the Prerequisites Dialog Box in Visual Studio 2010 or Visual Studio 2008. Then when you deploy with ClickOnce or Windows Installer, you can select this option to deploy the Microsoft Office 2010 PIAs to end-user computers. Microsoft office interop assemblies 16.0.0.0 keyword after analyzing the system lists the list of keywords related and the list of websites with related content, in addition you can see which keywords most interested customers on the this website.

1. Microsoft Office Interop Assemblies 16.0.0.0 2016
2. Microsoft Office Interop Assemblies 16.0.0.0 Free
3. Microsoft.office.interop.word
4. Microsoft Office Interop Assemblies 16.0.0.0 Download

Microsoft Office Interop Assemblies 16.0.0.0 2016

1. Trusted Windows (PC) download Microsoft Office 2007 Primary Interop Assemblies 12.0.6661.5000. Virus-free and 100% clean download. Get Microsoft Office 2007 Primary Interop Assemblies alternative downloads.
2. Oct 02, 2017  Hi, I wanted to know if the Primary Interop Assemblies Redistributable are available for office 365? If not, when will Microsoft make them available. The latest I could find are for Microsoft office 2010. Also, can the Microsoft Office 2010: PIA Redistributable installed on Microsoft Windows. Hi, As far as I know, there is no Office 2016/365.

-->

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.

• 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 Office Interop Assemblies 16.0.0.0 Free

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.Interop.SharePointDesigner.dll
Microsoft SharePoint Designer 14.0 Page Object Reference Library	Microsoft.Office.Interop.SharePointDesignerPage.dll
Microsoft Smart Tags 2.0 Type Library Note: Smart tags are deprecated in Excel 2010 and Word 2010.	Microsoft.Office.Interop.SmartTag.dll
Microsoft Visio 14.0 Type Library Microsoft Visio 15.0 Type Library	Microsoft.Office.Interop.Visio.dll
Microsoft Visio 14.0 Save As Web Type Library Microsoft Visio 15.0 Save As Web Type Library	Microsoft.Office.Interop.Visio.SaveAsWeb.dll
Microsoft Visio 14.0 Drawing Control Type Library Microsoft Visio 15.0 Drawing Control Type Library	Microsoft.Office.Interop.VisOcx.dll
Microsoft Word 14.0 Object Library Microsoft Word 15.0 Object Library	Microsoft.Office.Interop.Word.dll
Microsoft Visual Basic for Applications Extensibility 5.3	Microsoft.Vbe.Interop.dll

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

-->

Visual Studio offers features in C# and Visual Basic that improve Microsoft Office programming. Helpful C# features include named and optional arguments and return values of type dynamic. In COM programming, you can omit the ref keyword and gain access to indexed properties. Features in Visual Basic include auto-implemented properties, statements in lambda expressions, and collection initializers.

Both languages enable embedding of type information, which allows deployment of assemblies that interact with COM components without deploying primary interop assemblies (PIAs) to the user's computer. For more information, see Walkthrough: Embedding Types from Managed Assemblies.

This walkthrough demonstrates these features in the context of Office programming, but many of these features are also useful in general programming. In the walkthrough, you use an Excel Add-in application to create an Excel workbook. Next, you create a Word document that contains a link to the workbook. Finally, you see how to enable and disable the PIA dependency.

Prerequisites

You must have Microsoft Office Excel and Microsoft Office Word installed on your computer to complete this walkthrough.

Note

Your computer might show different names or locations for some of the Visual Studio user interface elements in the following instructions. The Visual Studio edition that you have and the settings that you use determine these elements. For more information, see Personalizing the IDE.

To set up an Excel Add-in application

1. Start Visual Studio.

2. On the File menu, point to New, and then click Project.

3. In the Installed Templates pane, expand Visual Basic or Visual C#, expand Office, and then click the version year of the Office product.

4. In the Templates pane, click Excel <version> Add-in.

5. Look at the top of the Templates pane to make sure that .NET Framework 4, or a later version, appears in the Target Framework box.

6. Type a name for your project in the Name box, if you want to.

7. Click OK.

8. The new project appears in Solution Explorer.

To add references

1. In Solution Explorer, right-click your project's name and then click Add Reference. The Add Reference dialog box appears.

2. On the Assemblies tab, select Microsoft.Office.Interop.Excel, version <version>.0.0.0 (for a key to the Office product version numbers, see Microsoft Versions), in the Component Name list, and then hold down the CTRL key and select Microsoft.Office.Interop.Word, version <version>.0.0.0. If you do not see the assemblies, you may need to ensure they are installed and displayed (see How to: Install Office Primary Interop Assemblies).

   Intermediate algebra 3rd edition pdf. InterServer Real Time Malware DetectionReal time suspected malware list as detected by InterServer's InterShield protection system.DNSRBL available at with lookups to rbl.interserver.netStatsInfo on 88.99.2.89Abuse DBID 722236First Seen 2017-12-26 03:16:16Last Seen 2019-09-30 01:19:17Reason 'modsecurity'Total Servers 61Total listings 149Error: Your IP may be getting blocked by our IPS due to a known string of false positive. Delist Me Abuse DB ONLY. Complete the reCAPTCHA then submit the form to delist.

3. Click OK.

To add necessary Imports statements or using directives

1. In Solution Explorer, right-click the ThisAddIn.vb or ThisAddIn.cs file and then click View Code.

2. Add the following Imports statements (Visual Basic) or using directives (C#) to the top of the code file if they are not already present.

To create a list of bank accounts

1. In Solution Explorer, right-click your project's name, click Add, and then click Class. Name the class Account.vb if you are using Visual Basic or Account.cs if you are using C#. Click Add.

2. Replace the definition of the Account class with the following code. The class definitions use auto-implemented properties. For more information, see Auto-Implemented Properties.

3. To create a bankAccounts list that contains two accounts, add the following code to the ThisAddIn_Startup method in ThisAddIn.vb or ThisAddIn.cs. The list declarations use collection initializers. For more information, see Collection Initializers.

Microsoft.office.interop.word

To export data to Excel

1. In the same file, add the following method to the ThisAddIn class. The method sets up an Excel workbook and exports data to it.

   Two new C# features are used in this method. Both of these features already exist in Visual Basic.

   • Method Add has an optional parameter for specifying a particular template. Optional parameters, new in C# 4, enable you to omit the argument for that parameter if you want to use the parameter's default value. Because no argument is sent in the previous example, Add uses the default template and creates a new workbook. The equivalent statement in earlier versions of C# requires a placeholder argument: excelApp.Workbooks.Add(Type.Missing).

     For more information, see Named and Optional Arguments.

   • The Range and Offset properties of the Range object use the indexed properties feature. This feature enables you to consume these properties from COM types by using the following typical C# syntax. Indexed properties also enable you to use the Value property of the Range object, eliminating the need to use the Value2 property. The Value property is indexed, but the index is optional. Optional arguments and indexed properties work together in the following example.

     In earlier versions of the language, the following special syntax is required.

     You cannot create indexed properties of your own. The feature only supports consumption of existing indexed properties.

     For more information, see How to: Use Indexed Properties in COM Interop Programming.

2. Add the following code at the end of DisplayInExcel to adjust the column widths to fit the content.

   These additions demonstrate another feature in C#: treating Object values returned from COM hosts such as Office as if they have type dynamic. This happens automatically when Embed Interop Types is set to its default value, True, or, equivalently, when the assembly is referenced by the /link compiler option. Type dynamic allows late binding, already available in Visual Basic, and avoids the explicit casting required in C# 3.0 and earlier versions of the language.

   Download game god of war 1 for pc. For example, excelApp.Columns[1] returns an Object, and AutoFit is an Excel Range method. Without dynamic, you must cast the object returned by excelApp.Columns[1] as an instance of Range before calling method AutoFit.

   For more information about embedding interop types, see procedures 'To find the PIA reference' and 'To restore the PIA dependency' later in this topic. For more information about dynamic, see dynamic or Using Type dynamic.

To invoke DisplayInExcel

1. Add the following code at the end of the ThisAddIn_StartUp method. The call to DisplayInExcel contains two arguments. The first argument is the name of the list of accounts to be processed. The second argument is a multiline lambda expression that defines how the data is to be processed. The ID and balance values for each account are displayed in adjacent cells, and the row is displayed in red if the balance is less than zero. For more information, see Lambda Expressions.

2. To run the program, press F5. An Excel worksheet appears that contains the data from the accounts.

To add a Word document

1. Add the following code at the end of the ThisAddIn_StartUp method to create a Word document that contains a link to the Excel workbook.

   This code demonstrates several of the new features in C#: the ability to omit the ref keyword in COM programming, named arguments, and optional arguments. These features already exist in Visual Basic. The PasteSpecial method has seven parameters, all of which are defined as optional reference parameters. Named and optional arguments enable you to designate the parameters you want to access by name and to send arguments to only those parameters. In this example, arguments are sent to indicate that a link to the workbook on the Clipboard should be created (parameter Link) and that the link is to be displayed in the Word document as an icon (parameter DisplayAsIcon). Visual C# also enables you to omit the ref keyword for these arguments.

To run the application

1. Press F5 to run the application. Excel starts and displays a table that contains the information from the two accounts in bankAccounts. Then a Word document appears that contains a link to the Excel table.

To clean up the completed project

1. In Visual Studio, click Clean Solution on the Build menu. Otherwise, the add-in will run every time that you open Excel on your computer.

To find the PIA reference

Microsoft Office Interop Assemblies 16.0.0.0 Download

1. Run the application again, but do not click Clean Solution.

2. Select the Start. Locate Microsoft Visual Studio <version> and open a developer command prompt.

3. Type ildasm in the Developer Command Prompt for Visual Studio window, and then press ENTER. The IL DASM window appears.

4. On the File menu in the IL DASM window, select File > Open. Double-click Visual Studio <version>, and then double-click Projects. Open the folder for your project, and look in the bin/Debug folder for your project name.dll. Double-click your project name.dll. A new window displays your project's attributes, in addition to references to other modules and assemblies. Note that namespaces Microsoft.Office.Interop.Excel and Microsoft.Office.Interop.Word are included in the assembly. By default in Visual Studio, the compiler imports the types you need from a referenced PIA into your assembly.

   For more information, see How to: View Assembly Contents.

5. Double-click the MANIFEST icon. A window appears that contains a list of assemblies that contain items referenced by the project. Microsoft.Office.Interop.Excel and Microsoft.Office.Interop.Word are not included in the list. Because the types your project needs have been imported into your assembly, references to a PIA are not required. This makes deployment easier. The PIAs do not have to be present on the user's computer, and because an application does not require deployment of a specific version of a PIA, applications can be designed to work with multiple versions of Office, provided that the necessary APIs exist in all versions.

   Because deployment of PIAs is no longer necessary, you can create an application in advanced scenarios that works with multiple versions of Office, including earlier versions. However, this works only if your code does not use any APIs that are not available in the version of Office you are working with. It is not always clear whether a particular API was available in an earlier version, and for that reason working with earlier versions of Office is not recommended.

   Note

   Office did not publish PIAs before Office 2003. Therefore, the only way to generate an interop assembly for Office 2002 or earlier versions is by importing the COM reference.

6. Close the manifest window and the assembly window.

To restore the PIA dependency

1. In Solution Explorer, click the Show All Files button. Expand the References folder and select Microsoft.Office.Interop.Excel. Press F4 to display the Properties window.

2. In the Properties window, change the Embed Interop Types property from True to False.

3. Repeat steps 1 and 2 in this procedure for Microsoft.Office.Interop.Word.

4. In C#, comment out the two calls to Autofit at the end of the DisplayInExcel method.

5. Press F5 to verify that the project still runs correctly.

6. Repeat steps 1-3 from the previous procedure to open the assembly window. Notice that Microsoft.Office.Interop.Word and Microsoft.Office.Interop.Excel are no longer in the list of embedded assemblies.

7. Double-click the MANIFEST icon and scroll through the list of referenced assemblies. Both Microsoft.Office.Interop.Word and Microsoft.Office.Interop.Excel are in the list. Because the application references the Excel and Word PIAs, and the Embed Interop Types property is set to False, both assemblies must exist on the end user's computer.

8. In Visual Studio, click Clean Solution on the Build menu to clean up the completed project.

See also