简体繁体 English

Outlook 2016 和 Office 365 中 vsto Outlook 加载项的不同行为

[英]Different behaviour of vsto Outlook add-in in Outlook 2016 and Office 365

原文 2021-10-26 17:52:27 6 1 outlook/ vsto/ outlook-addin

I've created a vsto outlook add-in which works well in my Outlook 2016 application but some of it's features doesn't work in Office 365 outlook.我创建了一个 vsto Outlook 加载项，它在我的 Outlook 2016 应用程序中运行良好，但它的某些功能在 Office 365 Outlook 中不起作用。 For example, when mail send event is triggered, in outlook 2016, mail.Sender is null until that mail is sent but in Office 365, value is assigned before sending the mail.例如，当触发邮件发送事件时，在 Outlook 2016 中， mail.Sender在发送该邮件之前为空，但在 Office 365 中，在发送邮件之前分配值。 Similarly, mail.SentOnBehalfName is null in Outlook 2016 but it contains sender's Display Name in Office 365.同样， mail.SentOnBehalfName在 Outlook 2016 中为空，但在 Office 365 中包含发件人的Display Name 。

Is there information in form of webpage or something available highlighting what changes are made in new versions of outlook with respect to VSTO add-in(I searched but could not find one).是否有网页形式的信息或可用的内容突出显示新版本的 Outlook 中对 VSTO 加载项所做的更改（我搜索过但找不到）。 Or is it on developer to test the plugin on various versions, debug to understand the differences and then find the solution for each outlook version?或者是开发人员在各种版本上测试插件，调试以了解差异，然后为每个 Outlook 版本找到解决方案？

1 个解决方案

Sender related properties are not guaranteed to be populated until the message is actually sent and moved to the Sent Items folder.在实际发送邮件并将其移动到“已发送邮件”文件夹之前，不保证会填充与发件人相关的属性。 This is not version specific.这不是特定于版本的。

If the sender is null, you can assume the default user account will be used ( Application.Session.CurrentUser ).如果发件人为空，您可以假设将使用默认用户帐户 ( Application.Session.CurrentUser )。