The Microsoft Office 2010 Primary Interop Assemblies (PIA) Redistributable is a Microsoft Windows Installer package that contains the Primary Interop Assemblies for Microsoft Office 2010 products. Breaking news from around the world Get the Bing + MSN extension. No thanks Add it now. This site uses cookies for analytics, personalized content. Office primary interop assemblies. 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. To make Microsoft® Office® XP applications available to Microsoft Visual Studio®.NET developers, Microsoft has created several primary interop assemblies (PIAs) that contain the official description of commonly used Microsoft Office XP type libaries for applications such as Microsoft Access 2002, Microsoft Excel 2002, Microsoft FrontPage® 2002, and more. The.NET Framework 4.5.2 Developer Pack installs the multi-targeting pack for.NET Framework 4.5.2. Developers can build applications targeting the.NET Framework 4.5.2 using either Visual Studio 2013, Visual Studio 2012 or third party IDEs.
- Microsoft Office Interop Assemblies 2016 2018
- Primary Interop Assemblies Redistributable
- Microsoft Office Primary Interop Assemblies 2016
Active3 years ago
I had to import an older project (in .Net 2) into Visual Studio 2013, it makes use of the Microsoft Primary Interop Assemblies.
Visual Studio said that I need to add references to the project. Now I went and did some reading and apparently Microsoft has only released the PIA for office 2010? (I have Office 2013)
Now what I would like to know is.
Microsoft Office Interop Assemblies 2016 2018
- Can I get it to work with office 2013 and be backward compatible?
- And if so is this a good route to go for the future? Is it going to be compatible? Because I see you need
.Net 2
(at the latest) and Windows 8 comes with 4.5 and not 3 (by default) and most new computers are going to have Office 2012 or 2013.
Primary Interop Assemblies Redistributable
13.6k44 gold badges4141 silver badges7979 bronze badges
ZapnologicaZapnologica9,8603434 gold badges112112 silver badges201201 bronze badges
5 Answers
PIAs are a historical artifact, required only by old .NET versions (before v4). They have been thoroughly and elegantly replaced by the 'Embed Interop Types' feature, also known as the 'No PIA' feature. Supported since Visual Studio 2010, you'll find it back in the Properties window when you select a reference assembly. It defaults to
True
. A good video that covers the underlying technology is available here.Which is the reason that Microsoft doesn't publish the PIAs for Office 2013, they expect you to embed the interop types instead.
The feature is very desirable, it avoids your customer having to install the PIAs on his machine and for you to include them with your installer. Solving the issue when neither takes care of it, an entirely too common mishap. In addition, the PIAs for Office are very large, the great advantage of embedding the interop types is that your assembly only contain the types that you actually use. Many megabytes reduced to a few kilobytes.
Microsoft Office Primary Interop Assemblies 2016
The workflow is a little different. Instead of adding a reference to the
Microsoft.Office.Interop
assemblies as available in the Add Reference dialog, .NET Framework tab, you now use the COM tab. And pick, say, 'Microsoft Excel 15.0 Object Library
' to generate the interop types for a program that uses Excel. If you load an old project that previously used PIAs then just remove those reference assemblies and add them back from the COM tab.Do note that a feature is lost, intentionally targeting an old version of Office that you don't actually have installed on your dev machine is more difficult. If that's a requirement then you still need the PIAs for that version, force the Embed Interop Types to True in the Properties window. Actually doing this is questionable, Microsoft has a hard time keeping new Office versions completely compatible with old versions. They've kept it up for 15 years now but it has been running out of steam. A worst-case scenario is targeting a newer version than you have installed on your machine, that's liable to make your program crash with very hard to diagnose exceptions like
AccessViolationException
. ![2016 2016](/uploads/1/2/4/8/124858009/484896225.jpg)
Do note that you have to make small modifications to your code to allow it to work. The synthetic '
Hans PassantHans PassantXxxxClass
' classes are not embedded, just the 'Xxxx
' interfaces. Simply remove the word 'Class
' from the new statement.816k114114 gold badges14041404 silver badges21882188 bronze badges
VS 2015 Community with Office 365 - for whatever reason the Add from the COM object does not work. The solution is go into the GAC and find the interop assemblies, copy them to a temp directory, then add to your project like any DLL.
Rob![Interop Interop](/uploads/1/2/4/8/124858009/552015740.png)
1,17655 gold badges2222 silver badges4545 bronze badges
Also, if you don't know by now, Windows 8 does have older versions of .NET Framework but they aren't installed by default. Go to Program Features ---> Add features to Windows ----> and the first check box should be .NET 3.0 and maybe 2.0. Note, if you are on a WSUS server you will need to tell Windows to grab the files from the Windows Update servers. Hope it helps!
amoor005amoor005
Officially there is no backward compatibility of the PIA for Office. In fact it works.
For backward compatibility reasons I'm using the PIA for Office XP since several years and it works fine with Office XP, 2003, 2007 and 2010 (not yet tested with 2013) and on Windows XP, Vista, 7 and 8.
For compatibility with the different versions of Windows I'm using the .NET framework 3.5.
For the future.. it depends of what you are doing with the PIA. If possible it is far better to directly deal with the Open XML files or to create an add-in for word/excel.
Free file shredder. LockHunter is a foolproof file unlocker It is a free tool to delete files blocked by something you do not know. LockHunter is useful for fighting against malware, and other programs that are blocking files without a reason. LockHunter is a foolproof file unlocker It is a free tool to delete files blocked by something you do not know. LockHunter is useful for fighting against malware, and other programs that are blocking files without a reason. Unlike other similar tools it deletes files into the recycle bin so you may restore them if deleted by mistake. FileASSASSIN is free software that can delete locked files deposited by a malware infection. Whatever the reason for the file, FileASSASIN can remove it. Aug 06, 2017 Free File Deleter software 1. Free File Unlocker. Free File Unlocker is a free software which helps users unlock and delete. Tizer Unlocker. Tizer UnLocker is again a simple and lightweight tool which comes. MoveOnBoot helps you rename, move or delete the locked files. Delete Files Permanently is a free file shredder program that supports more methods of sanitization than most of the other programs in this list, and you can even add custom data wiping schemes from the settings.
pmartinpmartin
I just found out that the Visual Studio 2013 express does not have office-support anymore. So you need at least the pro-version to make it work.
mr_w_snipesmr_w_snipes
Not the answer you're looking for? Browse other questions tagged visual-studio-2013office-interopoffice-2013 or ask your own question.
The working installation of Office corrupted following some Office updates yesterday and after trying all sorts of repair things etc I ended up uninstalling it so I could do a fresh install.
However, now when I try to install it I get the following error right at the end of the process:
1: 1935 2: {3194323D-C74C-40E0-A864-B677608E5D6E} 3: 0x80131049 4:
IAssemblyCacheItem 5: Commit 6: Policy.14.0.Microsoft.Vbe.Interop,
fileversion='15.0.4420.1017',version='15.0.0.00000000',culture='neutral',
publicKeyToken='71E9BCE111E9429C',processorArchitecture='MSIL'
IAssemblyCacheItem 5: Commit 6: Policy.14.0.Microsoft.Vbe.Interop,
fileversion='15.0.4420.1017',version='15.0.0.00000000',culture='neutral',
publicKeyToken='71E9BCE111E9429C',processorArchitecture='MSIL'
I have already tried the suggestion here https://answers.microsoft.com/en-us/msoffice/forum/msoffice_officeinsider-mso_win10-msoinsider_act/how-do-i-uninstall-office-365-windows-store/8fac43d0-4cb7-4d8a-8035-45547e5feb9c but it did not work for me.
This is a new laptop that's only had Windows, Office and a couple of other items like a printer installing so it's rather annoying that it's fallen over so soon!
Can anyone help please as I'm now going round in circles.
Thanks
Paul