This way, your users can continue to use your add-in solution in the new Outlook on Windows client. To help you plan and transition your existing solution to a web add-in, we’re focusing on closing this gap and developing support for these scenarios in web add-ins. We recognize that there are some scenarios that can currently only be implemented in VSTO and COM add-ins. Given the web-based nature of the new Outlook on Windows client, VSTO and COM add-ins aren’t supported. This creates a beautiful, modern interface that delivers a more consistent user experience with faster access to feature updates.Īlready have an existing Outlook web add-in? We invite you to test it in the new Outlook on Windows client and share your feedback on your experience with us and the developer community. The new Outlook on Windows desktop client in preview unifies the Outlook experience across platforms into a single web codebase. With the new Outlook on Windows client in preview, we’re launching initiatives to help ensure that your add-in solutions integrate seamlessly. Support for add-ins in the new Outlook on WindowsĮvery year, we focus on delivering features you need to enhance your Outlook add-ins and enable experiences not possible before. ![]() Assembling documents is much easier with Styles, file insertion, Fields and Content Control support. For example, citation management scenario is now unblocked with the support of Field, Footnote / Endnote, and Content Controls. With Word API 1.5, many user scenarios can be enhanced or unlocked. Now you can add, update or delete plain text content controls. Plain text content controls are supported across platforms. ![]() For example, show different content to users when they navigate among rich text content controls. With these events, add-ins can provide more interactive experience for end users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |