Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Outlook for Windows *Preview Release* does not currently provide third-party interoperability: OGCS won't work #1640 #1666

Closed
huotg01 opened this issue Jun 22, 2023 · 4 comments
Labels

Comments

@huotg01
Copy link

huotg01 commented Jun 22, 2023

This is not really a bug report. It is an information related to ticket #1640

I don't know the value of the information, but in this post (https://lazyadmin.nl/office-365/new-outlook-for-windows/), there is this:

No Support for COM/VSTO Add-in
Microsoft is not planning to support COM and VSTO Add-ins at the moment. These types of add-ins are often used in corporate environments. Microsoft encourages developers to switch over to Web Add-in based on OfficeJS. The lack of support for COM and VSTO add-ins can really hold back the adoption in corporate environments.

What is "Web Add-in based on OfficeJS" ?

Gaston

@huotg01 huotg01 added the bug Something's not working right label Jun 22, 2023
@phw198
Copy link
Owner

phw198 commented Jul 2, 2023

Oh the irony - the lazy admin website's certificate is invalid 😆

OfficeJS is basically "JavaScript API for Office" web-based add ons. Seems the lazy admin didn't check very far with their comment to switch over to it - there is currently no OfficeJS Outlook API available either!

However, I would agree with the comment on corporate environments - most will have line of business applications dependent on COM, and therefore won't be able to adopt the New Outlook until either Microsoft support COM, or vendors have time to rewrite their products for the JavaScript API.

It's just too early to tell....

@phw198 phw198 added question and removed bug Something's not working right labels Jul 2, 2023
@redfearnb
Copy link

I did try the New Outlook PWA or whatever they're going to call it. It works fairly well and didn't exactly kill OGCS working at the same time, because the same Outlook services seem to be running in the background to make the web UI version of the "New Outlook" work. However, I did start getting an error message saying multiple copies of OGCS were running; they were not.

In any case, because the "New Outlook" is still missing features I use, I switched back to it after trying it out for a couple weeks.

@phw198
Copy link
Owner

phw198 commented Apr 6, 2024

@redfearnb I think the multiple copied of OGCS was fixed in #1717 and v2.10.2, but I'd be interested to know how "broken" OGCS gets against the New Outlook. If you try it again, would you be able to provide logfiles?

@phw198
Copy link
Owner

phw198 commented Jun 16, 2024

Cross referencing more detail for the OP at #1734.

For early development builds of a version that doesn't require the Outlook client to sync, please see:-

@phw198 phw198 closed this as completed Jun 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants