适用于 Lync 的 UCC API 到 UCMA 3.0
我有一个为 LCS 编写的项目，它使用 Microsoft.Office.Interop.UccApi.DLL，现在我将通过使用从 Microsoft.RTC.Collaboration.dll 生成的 .tlb 文件将 C++ 的 UCCAPI COM 更改为 UCMA 3.0 来进行返工（从托管 dll 到本机的互操作），所以我想知道是否有我可以寻找的由 C++ 编写的示例或 SampleApps？
我正在尝试使用命名空间 Microsoft.Rtc.Collaboration，但它不起作用
“.tlb”文件的大小只有 2k（从 5M .dll 生成），所以我不确定它是否会起作用
任何建议？
非常感谢
I have a project written for LCS that uses Microsoft.Office.Interop.UccApi.DLL, now I'm going to rework by changing the UCCAPI COM for C++ to UCMA 3.0 with the .tlb file generated from Microsoft.RTC.Collaboration.dll (interop from managed dll to native), so I wonder are there any examples or SampleApps written by C++ that I could look for?
I'm trying with using namespace Microsoft.Rtc.Collaboration, it didn't work
The size of ".tlb" file is only 2k (generated from 5M .dll), so I'm not sure that it'll work
any advises?
Many thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
从 UCCAPI 迁移到 UCMA 3.0 一点也不简单 - 两种对象模型完全不同，并且针对不同的平台（UCCAPI 通常用于客户端，UCMA 则用于服务器端）。我确信您最终将不得不完全重写使用 LCS/Lync 功能的逻辑。
一种选择是继续使用 UCCAPI - Lync 仍支持它，但下一版本将弃用它（请参阅支持通知 此处）
如果您想使用较新的 API，那么我怀疑您的应用程序将被重写，但值得长期来看。首先决定是采用 Lync API 路线（对于客户端应用程序）还是 UCMA 3.0 路线（对于中间层服务器端应用程序）。
如果您要完全重写应用程序并且具有 C# 技能，那么使用 C# 将是推荐的路线。否则，托管 C++ 是一个选择吗？如果失败，您可以包装所选的 Lync API 并将其公开给 COM 以从现有应用程序调用它。
Migrating from UCCAPI to UCMA 3.0 will not be straightforward at all - the two object models are completely different, and target different platforms (UCCAPI is generally used client-side, UCMA is server side). I'm sure you will end up having to rewrite the logic that uses LCS/Lync functionality completely.
One option would be to keep using UCCAPI - it is still supported against Lync, although it will be deprecated for the next version (see the support notice here)
If you want to go with the newer APIs then I suspect your app will be a rewrite, but worth it in the long term. First decide whether to go down the Lync API route (for client-side apps) or the UCMA 3.0 route (for mid-tier server side apps).
If you're rewriting the app completely and have C# skills, then using C# would be the recommended route. Otherwise, is managed C++ an option? Failing that, you could wrap the chosen Lync API and expose it to COM to call it from your existing app.