WordAPI | natural language webservice and API for document | Natural Language Processing library

We recently created a Word Add-in that uses WordApi 1.3. A client of ours uses a Volume License (VL) version of Word 2016 [Word 2016 MSO (16.0.4849.1000) 32-bit].

As per the Word Javascript API requirement set the Office 2016 version build should be at least Version 1612 (Build 7668.1000). The client's version/build is indeed not supported, since the add-in does not sideload and is not visible to them in the AppSource store.

Our app's requirements are:

I'm trying to setup buffalo to send data to AWS X-Ray. I am new to buffalo/go and I'm completely lost in the docs...

My actions.go

I am developing a Windows application where I manipulate Word Application. More specific, I am opening a Word Document but when I quit it and try to open another Word Document this Error comes out.

How to handle

System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) at Microsoft.Office,Word.ApplicationClass.set_Visible(Boolean Prop)**

If I don't quit the Word Application this error does not come out.

Below I show you the functions that I open and quit the Word Application.

When submitting our addIn we got the following message back:

If you do not support 2013 SP1 because you are using an API only available in 2016/Online, you must put these apis in the requirements tag in your manifest.

Our addIn does not work in Office 2013 since it uses both WordApi and ExcelApi (When opened in Word and Excel accordingly) which is not available in Office 2013.

Therefore we tried to specify in our manifest file that our addIn requires WordApi 1.1 by adding this to the manifest file:

I am trying to develop Alexa skill, which would find sample sentences to the word user says. I found API for this (WordAPI), although when I am making a call, response is undefined. Can someone help ?

My code:

According to Microsoft's Office add-in documentation. the Requirements element in the manifest specifies "... the minimum set of JavaScript API for Office requirements that your Office Add-in needs to activate."

I can't figure out the correct place to put that element. The above-linked documentation says Requirements is a child of OfficeApp, but the Seller Dashboard and the manifest validator both say that is incorrect:

Details: The element 'OfficeApp' in namespace 'http://schemas.microsoft.com/office/appforoffice/1.1' has invalid child element 'Requirements' in namespace 'http://schemas.microsoft.com/office/appforoffice/1.1'. List of possible elements expected: any element in namespace 'http://www.w3.org/2000/09/xmldsig#'.

All the docs I've read, SO questions, etc., only include snippets like:

I have an Office add-in/TaskPane app.

When I try to specify the requirements set for this app in my manifest.xml, I am getting the following error from office-addin-validator:

The element OfficeApp in namespace http://schemas.microsoft.com/office/appforoffice/1.1 has invalid child element Requirements in namespace http://schemas.microsoft.com/office/appforoffice/1.1

The documentation makes it very clear that Requirements is in fact allowed in this location.

I am able to add the requirement set inside the VersionOverrides tag, and that section looks like:

Problem Found! I scrubbed stackoverflow and found: this. This appears to be the issue. Browsersync has funny behavior that leads to these issues occurring. So my new question is: How does one deploy a word add-in without browser-sync? I've tried running tsc and node directly on the app.ts and app.js respectively, but that just gives me an error: ReferenceError: Office is not defined

I am new to developing office add-ins. I have an add-in that works when I have one document open. If I have multiple documents open, the behavior that I expect is that the add-in's functions, when actuated, should apply only to the document in focus.

This does not actually happen. I've done multiple tests, and can't quite figure out what is going on. Sometimes, pressing a button in the add-in window of the second opened document will perform actions on the first open document. Sometimes, on the second.

EDIT: Here is a minimal working example:

I'm working on an add-in used in Word (already published and used). Our requirements are Word 2016 but that should be it as far as I know. Usually, when we had users complaining about not being able to install our add-in, it turned out they had an older version of Word etc.

This is in our manifest file: