Cannot add reference to Outlook 2016 (Office 365) Interop

I am actually trying to add a recommendation to ‘Microsoft Outlook 16.0 Things Public Library’ in a C#. INTERNET 4.6.1 WPF venture, because I have office 2016 mounted. Previous variations of the Item Library are actually irreconcilable with the 2016 model of office.

If I make use of Excel’s VBA editor, ‘Microsoft Overview 16.0 Object Library’ is noted, and exists in C: \ Program Documents \ WindowsApps \ Microsoft.Office \ Microsoft Shared \ OFFICE16 \ MSOUTL.OLB, as you may view below:

However a lot more importantly, if I have office put up, as well as I can access ‘Microsoft Overview 16.0 Things Collection’ from Excel Vba, after that why can’t I access it from Visual Workshop?

There is actually undoubtedly some issue with the setup misunderstanding the dlls appropriately, just Excel has some trick it utilizes to produce the recommendation offered anyway.

Specifying on my earlier remark: From what you have actually illustrated, it seems like you’ve installed a 32-bit version of Microsoft Office on a 64-bit device. Just 32-bit COM items would have been registered, as well as a result a 64-bit. INTERNET use would be incapable to locate them. You ought to locate that the course ID is simply registered under the Wow6432Node if you look your computer system registry.

To solve the issue, you could possibly either mount the 64-bit variation of Office or even pressure your.NET treatment to target the x86 platform.

Quite why Dell believe we really want 32 bit models put in on 64 little equipments, or even why a person coming from Microsoft hasn’t uploaded a remedy to this issue, is actually past my understanding, but regardless, RogerN was correct. Because of everyone for taking opportunity out their days to aid me out.

Yet it carries out not give total model, like “Office 2016 Professional Additionally” or “Office 2016 basic”.

Worth taking note is that my version of office is actually mounted as a ‘Microsoft Window Establishment Treatment’ as well as for that reason does certainly not look on the typical Add/Remove courses list, so I can’t locate any type of ‘repair service’ possibilities for the installment.

When I make use of Visual Workshop, the COM tab performs certainly not list ‘Microsoft Office 16.0 Item Library’, and also when I attempt to explore to C: \ Course Reports \ WindowsApps, i receive ‘You do not presently possess permission to accessibility this folder’, and clicking on ‘Continue’ (to obtain gain access to) results in ‘You have been refuted authorization to gain access to this directory’.

Generally, the Office 2016 dlls seem to have been actually tucked away in a file that is hard to reach to male, pet dog, as well as neighborhood administrator.

All I am actually trying to perform is hook up to the open Overview application, and after that send out an email along with an accessory, so maybe another question to talk to is actually, exists some new fangled technique to interact along with Overview 2016 that have not surfaced in my Googleathon?

I am actually attempting to incorporate a recommendation to ‘Microsoft Overview 16.0 Object Collection’ in a C#. INTERNET 4.6.1 WPF venture, due to the fact that I have office 2016 mounted. Previous versions of the Things Public library are actually inappropriate with the 2016 variation of office.

I can receive Microsoft office put up version with the aid of pc registry, for example “Office 2016 (64 little)”.

I do not think accessing the WindowsApps directory is actually the way to go. It is actually secured down for some reason which normally suggests the possibility for problem if i begin digging around as well as modifying safety and security permissions, not to point out the truth that preserving a copy of the latest dll in my answer will definitely incorporate needless difficulty to my task.

Elaborating on my earlier comment: From what you’ve explained, it appears like you have actually put in a 32-bit variation of Microsoft Office on a 64-bit equipment.

Leave a Reply

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