Can’t locate Microsoft.Office.Interop in Reference List

I was provided this option to an issue I had, given that I didn’t know how to incorporate MS Word with C#:

I checked out this solution, and I cannot locate Microsoft.Office.Interop.Word in the recommendation list. I can’t discover it under COM Things either. What am I missing? I am utilizing Visual Studio Express 2012.

The answer to this question is that you HAVE to install MS Office on your computer system.

You must set up the Microsoft Office main interop assemblies (PIAs) in the international assembly cache of your advancement computer system prior to you can perform particular development jobs. Typically, the PIAs are installed instantly when you install Office on the advancement computer system. However, sometimes you might have to set up the PIAs independently.

You may likewise use NuGet Package Supervisor in order to set up the reference. Go to Project -> Manage NuGet Plans … Browse for “Interop.Word” and install that plan.

Examine if the library (Microsoft.Office.Interop.word) exists in the assembly folder of windows (C: \ Windows \ assembly) else you can install it from

Now you just need find it in your visual studio.

Click on the consoleApplication( or name of you application) in SolutionExplorer window and

Go to Include -> Referrals- > Browse and discover C: \ Windows \ assembly \ GAC_MSIL \ Microsoft.Office.Interop.word or comparable directory. press ok and your can now use the library in your application.

I have currently developed Oulook Include on using Visual Studio 2010 with VSTO

It works for OFFice 2007, 2010 and 2013

Now Office 2016 has actually been launched. is the exact same application will work for 2016?

Is there any modifications in VSTO and PIA Variation for Office 2016? is those has been launched?

if not when will be released? is there any websites to track the release?

If any, Whether i need to set up those?

Appreciated for getting an advancement guidance in Office 2016

In theory, the exact same add-in can be utilized in 2016. No significant changes have been made to VSTO; about the item model (exactly what’s shown in the PIA) you have to ask in an Outlook-specific group. Office 2016 has been released, already months ago.

It doesn’t matter exactly what PIA variation you utilize in the task. The add-in should work properly until you use members introduced in newer Office variations. Find out more about that in the Running Solutions in Various Versions of Microsoft Office short article.

Keep in mind, you can utilize the late-binding technology for accessing properties, approaches and occasions in more recent Office variations even when utilizing older PIAs. See Type.InvokeMember.

There is no different installer for Office 2016 PIAs. You can install them as a part of Office 2016. See The Best Ways To: Install Office Primary Interop Assemblies to learn more.

I have a c# (VS 2015) application that references Microsoft.Office.Interop.Excel

My code consists of oXL = brand-new Microsoft.Office.Interop.Excel.Application(); along with the above referral.

If I assemble and set up that application on a maker that already has both Office 2013 and.Net 4.0 but when I search that computer system I can not discover Microsoft.Office.Interop.Excel.dll on it anywhere which, I assume, is what I need.

The .NET application will look for the dll in the global assemblies and bind to whatever appropriate dll there is dynamically. edit excel in .NET

DLL = dynamically linked library

There are various dlls for dofferent variations of office and on various platforms (32 bit versus 64 bit). In other words, do NOT include the dll in your package. Capture exceptions in case office is not installed.

Leave a Reply

Your email address will not be published. Required fields are marked *