我不知道它是否可以发送会议请求，以人无需安装在服务器上的Outlook，并使用COM互操作（这是我想避免服务器不惜一切代价的）。

I just wonder if it is possible to send Meeting Requests to people without having Outlook installed on the Server and using COM Interop (which I want to avoid on a server at all costs).

我们有Exchange 2003在Windows 2003域和所有用户都是域中的用户。我想我可以把'轮的iCal /的vCal或东西，但我不知道是否有发送会议通过交换请求没有Outlook的恰当的标准方法是什么？

We have Exchange 2003 in a Windows 2003 Domain and all users are domain Users. I guess I can send 'round iCal/vCal or something, but I wonder if there is a proper standard way to send Meeting Requests through Exchange without Outlook?

这是C＃/。NET，如果它很重要。

This is C#/.net if it matters.

推荐答案

发送会议请求的Outlook（并有它识别）的方式是这样的：

The way to send a meeting request to Outlook (and have it recognized) goes like this:

prepare显示iCalendar文件时，一定要设置这些附加属性，如Outlook需要它们： UID 序 创建的 最后一次修改 DTSTAMP prepare an iCalendar file, be sure to set these additional properties, as Outlook needs them: UID SEQUENCE CREATED LAST-MODIFIED DTSTAMP 第1部分：的text / html （或任何你喜欢） - 这是显示为普通邮件阅读或作为后备，并包含了一个总结事件在人类可读的形式 第2部分：文本/日历;方法=请求，持有ICS文件（头方法参数必须在ICS的方法相匹配）的内容。当心正确的文本编码，宣布一个字符集头参数将不会受到伤害。 第3部分：可选，附加的.ics文件本身，所以普通邮件的读者可以提供给用户的东西点击。 Outlook不真正需要的附件，因为它只是读文本/日历部分。 Part 1: text/html (or whatever you like) - this is displayed to "ordinary" mail readers or as a fall-back and contains a summary of the event in human readable form Part 2: text/calendar; method=REQUEST, holds the contents of the ics file (the header method parameter must match the method in the ics). Watch out for the correct text encoding, declaring a charset header parameter won't hurt. Part 3: Optionally, attach the .ics file itself, so ordinary mail readers can offer the user something to click on. Outlook does not really require the attachment because it just reads the text/calendar part.

有关详细信息和ICS文件格式的特点帮助下，一定要通过雅秀神崎。他们是在黑暗中一盏灯，不是通过 RFC啃着自己的方式2445 的要好得多。但话又说回来，也许一个方便的图书馆存在.NET。

For help on the details and peculiarities of the ics file format, be sure to visit the iCalendar Specification Excerpts by Masahide Kanzaki. They are a light in the dark, much better than gnawing your way through RFC 2445. But then again, maybe a handy library exists for .NET.