In one addin, we intercept and parse the email before it is sent to see if it will allow Outlook to send it or not. Problem: Below I'll provide two use cases where the Outlook Web Addin is very with the presence of a COM addin. If I have to state ONLY one benefit of COM over office.js in Outlook, I'd say that office.js lacks the support of inboxes that not use Exchange server as a backend, so Gmail, Yahoo and 3rd-party email providers are not supported which is too frustrating and we should keep the COM addin there. Now, on Windows, we have both addins running for Outlook the COM & Office.js one but as far as I can tell, there is no comparison between the two, the COM addin is far more superior than the equivalent Web Addin. So, as I already have clients who use COM Outlook addins, which works more than perfect for their needs, they just needed a way to have the same addin on Mac, Web and Mobile, and I spend some time learning how to build addins using office.js and did deliver some good results but after they started using the new addin, some unexpected drawbacks flopped to the surface which made me think twice!
The ONLY clear benefit is the multi-platform support. We have to agree that Outlook Web Addins (and office.js addins in general) are not mature enough to completely replace COM/VSTO/VBA addins. This worked for me very well at the beginning but it quickly turns out, in some situations, to be terrible, or at least in two of my cases.
My background is the COM/VSTO land and due to new requirements, I'm slightly merging to office.js.įirst, I was very pleased by the concept that unlike Word, Excel & PPT ofiice.js add-ins, Outlook Web Add-ins install directly on the user's exchange inbox, which means: install once, run everywhere. Well, that's a very important thing, or at least, I think it is, so, please read it carefully.
0 kommentar(er)
