I have VSTO word addin and I have put a button in the ribbon and a label (company name).
On button click, I get selected text and pass this selected word as a queryparam to my application as below: www.myapplication.com?selectedtext= [getselectdwordfromword]
We have few clients and all have a different application name.
So how can the client set his application URl and label (company name)?
Is there any way so we can provide configurations and client changes configurations based on their requirements before installing VSTO in their system?
Thanks in advance
You can develop a custom UI for the add-in installer where your customers can enter the required application URL and company name. So, at runtime you could read such values from the windows registry or any other place where the add-in installer could write down these values after installing. The Deploy an Office solution by using Windows Installer article describes all the required steps for creating MSI installers.
Related
We run some custom add-ins in Outlook application and occasionally find that the Outlook application disables them; I then have to manually go to the application settings and re-enable them on each users PC. We are running Microsoft Office 365 click to run applications. I have tried the following but nothing seem to work 100% of the time.
I have tried setting the "AddinList/ProgID" REG key to 1 (always enabled) as described here - https://learn.microsoft.com/en-us/office/vba/outlook/concepts/getting-started/support-for-keeping-add-ins-enabled.
I have also tried setting a number of registry key combinations as described here - https://www.konnectemail.com/prevent-outlook-add-in-from-getting-disabled
Is there a specific way to tell the office application to NEVER disable a particular add-in regardless of the Office version?
I have a published/certified MS Outlook Add-In on the Microsoft Store:
https://appsource.microsoft.com/en-us/product/office/WA104381281?src=office&tab=Overview
It shows Product Supported: OfficeProductForAndroid and OfficeProductForIOS. However, the Add-In only appears on IOS devices (as well as Desktop, OWA, etc).
How can I get support to know why the Add-in does not appear on Android devices?
PS - it does work by adding our XML staging manifest directly. And other public store Add-Ins are working.
In mobile(iOS and Android) add-in need to be whitelisted to show on Add-in Management Screen if it is not installed manually or not installed at all.
Whitelisting of Add-in is done by our team on request. I think franConnect has been whitelisted. Soon it will start coming on Addin Management Screen.
I am trying to understand how to develop add-ins/macros in JS for Office, do I need VSTO for it or does it run from Office somewhere?
I did understood that Microsoft is making the first steps toward replacing VBa with JS and impemented an API to develop macros in Office.Js simmilar to the one Google has for it's Docs. But where can I find a development enviroment for Office.js?
The new web-based add-ins are basically a web application executed in the context of the Office application, either on the Desktop (by embedding a browser, IE11 at the moment) or in the browser (Office Online) where everything is web-based already.
The add-in can be hosted on any web resource you like. You just need to specify a source location URI.
Settings and metadata of the add-in are defined in a manifest file. The article Office Add-ins platform overview describes it very well.
Development can be done in any editor or IDE suitable for coding web apps. There is no Alt+F11 VBA IDE anymore, but you may try the Script Lab add-in, a Microsoft Garage project that allows you to try out some code directly in Office and share code snippets. It includes a great collection of sample code too.
The new WebApplications are hosted on a Webserver. You can develop Office Apps with Visual Studio.
Here is a good course for developing Office Apps including an overview of the Javascript Office API:
https://mva.microsoft.com/en-us/training-courses/introduction-to-office-365-development-8329
I have outlook 2016 with MS Vision 2013 installed. When I try to open MS visio file from Harmon.ie, I get License error message.
Error:
Microsoft Office cannot verify the license for this product. You should repair the office program by using control panel.
I can open the MS same MS Visio drawing manually or from sharepoint with no problem.
This error message could not be directly related to harmon.ie. You need to reach out to Microsoft about it. You should reproduce it out of harmon.ie.
Indeed, when user clicks on a document - harmon.ie (as a client application versus web interface) determines appropriate application based on the document extension and then launches the associated desktop application by passing it the URL to the document. Running the application from command line and passing it the direct URL of the Visio document duplicates the behavior of opening the document via harmon.ie. You can get the url to your Visio document by right clicking on it from our sidebar, and select copy address.
Please check again to see if running MS Visio, from command line and providing the URL to the SharePoint document would reproduce the issue:
-Open a cmd window
-Sample command format is below
"Path_to_Visio\visio_exe.exe" "urlof_document/document.visio_extension”
----- Jean
I developed an add-in with a MessageComposeCommandSurface extension point.
It appears, is activated and works on outlook.office.com but with windows desktop client, Outlook 2016 (version 16.0.8625.2121), the button appears in compose mode but stays gray and it is not clickable.
I tested the command-demo-addin mentioned in Microsoft Docs and published on Github with the same result. Similarly, as shown on screenshot, it is impossible to click and launch the add-in which seems unactivated.
The COMPOSE buttons are disabled in the following instances:
1) The Item is in a public folder.
2) The Item is in Junk, Outbox (not drafts), or Sync Issues.
3) The item is "secure". DRM, or S-MIME encrypted. (older versions of Outlook also do not support S-MIME signed)
4) Outlook is offline.
In the situation where Read Mode add-ins are working, but Compose does NOT it is almost always #3. Usually the user will have on the option to always DRM / S-MIME their outgoing messages.
Update with image of security settings:
If Com Add-ins load a Custom Form this can also affect add-ins:
Checking Com Add-ins:
Note that outlook actually ships with some add-ins and a lot of com-addins work fine with Web Add-ins. It's only when Com Add-ins override the default new mail form (or other forms) that they can interfere with Web Add-ins.
Some COM add-ins will NOT use Custom Form, but will access the parent folder (item.Parent) and there is currently a bug that disable's Web Add-ins when a COM Add-in or VBA script does this.
File->Options->Add-Ins-> "Go" (next to manage add-ins)
If you have an antivirus instaled like avast, try to disable the addin of this and then try to open your compose mail window.