Just faced with strange behavior on Outlook for Mac. When a user creates an event, add attendees, save and close, then select it and press the button "Forward" it opens a new message window with disabled my Outlook Add-In (open Add-in button is disabled). When I do the same on Outlook for Window the Add-in button is enabled and Add-in works fine.
What is the reason to change behavior on Mac and Windows? Is it an issue?
Stable repro, I use the same o365 account (there is no difference between the Add-in manifest then), Outlook for Mac 16.36 (20030502), Outlook for Windows 2006 (build 13001.20384 Click-to-Run) Current chanel.
Thanks in advance.
Sorry for confusion earlier. We do not support add-ins in the event forward scenario by design in Outlook Mac.
However, read mode add-ins are supported in event forward scenario (with the exception of item.getBody APIs) in the New Outlook for Mac, which is currently available in our Insiders program. You can get access to it by signing up for the Insiders program here.
Related
I have written an add-in for Microsoft Excel. The add-in works great on the web-based Excel, but I get the error below when I try to run it in the desktop version
This happens when the plugin tries to authenticate the user using a popup window. Anyone encountered this issue ?
Thanks
Matteo
I've seen posts from several years ago stating that automation wasn't supported in older click to run installations of Office, eg 2010. Can anyone tell me if this is still the case with Office 365?
For background, the reason I'm asking is I support some .NET desktop applications which use late-binding to automate Excel and Word. They've worked fine for all users until a recent client who has Office 365 Business click to run. On this PC (and this one only, so far) the app fails ("Cannot create ActiveX component") at the line:
Dim oExcel as Object = CreateObject("Excel.Application")
User claims Excel is definitely installed and working (and Registry key at /HKEY_CLASSES_ROOT/Excel.Application/Curver confirms 2016 is present.) Also CreateObject("Scripting.FileSystemObject") executes correctly, so it doesn't seem to be a scripting problem.
Thanks for any assistance!
We build an Outloook Addin and are testing it across different platforms.
It works on all the browsers (IE 11, Edge, Chrome and Safari), but not in the Outlook 2016 on Windows 10.
We root cause it, looks like the problem is Office JS API UI.displayDialogAsync() .
It does not open a dialog in Outlook 16 and the addin just hangs in there with the following progress message spinning forever,
[Your Addin] is working onr your [Request]
The closest thing we found on the Internet is this Stackflow post in which the answer says
the oldest Outlook build that supports this API is 16.0.6741.0000.
We are using 16.0.9226.2114, so we meet the requirement.
Here are versions of OS/Outlook and Office JS we use in the test:
OS: Window 10 Home, Version 10.0.16299, x64
Outlook: 16.0.9226.2114, 32bit (Version 1804)
Office JS: 1.1.5-release-next.1 (We download the exact package from GitHub and host it on our server)
Wonder is there any known issue of this API on Outlook 2016? Need some help here, thanks!
We have also been trying to debug Outlook 2016 using F12 developer tools .
But our addin cannot show up in the chooser page, no matter we launch the chooser before or after
we click on our addin. We have tried this on several windows 10 machines, but none of them work. Any suggestions that what we could possible miss here?
Seems to me that you had a similar issue to mine. For me adding the remote domain in the manifest resolved the case. Find and update the following section:
<AppDomains>
<AppDomain>https://your.domain.com/</AppDomain>
<AppDomain>https://auth.com/</AppDomain>
</AppDomains>
Proxy HTML works cause it's loading from your domain and still is viable solution.
I have a VSTO Excel 2010 workbook project, and it works on all PCs except one. The additional custom user control isn't present on the workbook. I've noticed that exceptions in C# are suppressed, and I haven't found where they can be viewed. Is there such thing as Excel error log? How do I turn on all error messages?
There are (2) error log sources that office uses when errors occur. "Microsoft Office Diagnostics" and "Microsoft Office Sessions". You can try to use these to troubleshoot.
Office 2010
You can enable interface error dialogs by going to File->Options->Advanced->Developers and checking "Show Add-in user interface errors".
Office 2007
You can enable interface error dialogs by going to Tools->Options->Other->General->Advanced Options and checking "Show Add-in user interface errors".
There is also an option to enable logging (unsure of its behavior)
I wrote a Word 2003 add-in that uses the 2003 PIAs for early-binding. I want the same executable to support the Ribbon interface in Office 2007 and 2010, while still running in Office 2003.
Is it possible to late-bind the IRibbonExtensibility interface? If not, is there another way to dynamically differentiate between Office versions?
There's a good book on working with the ribbon UI in Office:
RibbonX: Customizing the Office 2007 Ribbon
Robert Martin, Ken Puls, Teresa Hennig
The authors and MS both suggest a trick along these lines for solving this problem:
When your add-in loads, it queries the app to find out what version it's running in.
If Office 2003, it creates a normal CommandBars 'n Buttons UI.
If Office 2007 or later, it looks for another add-in and demand-loads it. This second add-in contains just the RibbonX code to create your ribbon UI plus handlers for the button click events. The handler simply calls back to the main add-in.
With a little clever use of tags in your RibbonXML and handler, you can have a single handler work out which routine in the main add-in to call.