开发 Microsoft Office 套件集成产品时的注意事项
我有一个产品创意，需要集成到 Microsoft Office 套件中。
是否需要注意任何许可/限制问题才能继续？
I have a product idea that requires integration into the Microsoft Office suite.
Are there any licensing/limitation issues to be aware of for me to proceed?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
取决于...
如果您的产品使用他们发布的 API，并且您没有在“您的盒子里”运送他们的任何组件，那么您（可能）只是他们平台之上的增值供应商。 您将告诉您的客户安装适当的 MS 产品，然后在顶部安装您的应用程序。 这种方法很好，您需要告诉 MS 的唯一原因是，如果您是首选/认证的供应商/合作伙伴，您将获得更多业务。 （根据您要集成的产品，您应该检查 MS 以确保使用它们时没有特定的许可条款）。
如果您将他们的任何代码放入您的盒子中，那么您必须确保您在他们的许可条款内操作，并且他们几乎肯定会让您跳过一些障碍以获得他们的批准。 您还面临着分享收入的问题，这不太可能对您有利。
根据我的经验，MS 不喜欢对任何人这样做——无论规模大小——尤其是非常小的玩家。
您最好在开始之前直接联系他们，看看是否有您可以加入的孵化项目来表达您的想法。
Depends...
If your product uses their published APIs and you don't ship any components of theirs "in your box" then you are (probably) just a value added supplier on top of their platform. You would be telling your customers to have the appropriate MS products in place and then install your App over the top. That approach is fine and the only reason you need to tell MS is because you will get a lot more business if you are a preferred/certified supplier/partner. (Depending on which product(s) you are integrating with you should check on MS to make sure that there are no specific license terms around using them).
If you put any of their code in your box then you have to make sure you are operating within the terms of their license and they will almost certainly make you jump through some hoops to get yourself approved by them. You also have the problem of sharing revenues which is not likely to work in your favour.
In my experience MS don't like doing this with anyone - regardless of size - and certainly not with really small players.
You may be better off approaching them directly before you start and find out if there are incubation projects that you could join to surface your idea.
我意识到我也有一个技术答案给你。 大约 10 年前，我编写了一个 Excel 插件，它利用他们的电子表格来显示来自我的提供商的数据。 它非常成功，作为一种可行的创收产品存在了大约 8 年。 这是我当时工作的 BI 公司的一个关键差异化因素。
我们代码库中最令人头疼的问题是 Excel 版本之间 API 的差异，以及不同的 DLL 依赖关系。 MS 喜欢说他们不会在版本之间破坏 API，但事实并非如此。 他们可能在这方面做得更好，但对于我们来说，获得他们新软件的预发布版本来看看我们必须做什么才能让我们的软件正常工作始终是一个真正的问题。 然后我们必须支持几个不同的 Ecel 版本并在它们之间升级我们的内容。 总而言之，它给我们的生活增加了巨大的复杂性。
他们的 API 在风格上发生了显着变化，Office 比以前更加开放，但你要求考虑因素，这肯定是其中之一。
I realised I have a technical answer for you too. About 10 years ago I wrote a plug-in for Excel which leveraged their spreadsheet to surface data from my provider. It was very successful and lived for about 8 years as a viable revenue generating product. It was a key differentiator for the BI company I worked for at the time.
The major headache in our code base was differences in API between versions of Excel, plus different DLL dependencies. MS like to say that they don't break their APIs between releases but this is not actually true. They may have got better at it, but it was always a real issue for us getting hold of a pre-release version of their new software to see what we had to do to keep ours working with it. Then we had to support several different Ecel versions and upgrade of our content between them. All in all it added a huge amount of complexity to our lives.
Their APIs have changed significantly in style, and Office is much more open than it was, but you asked for considerations and this is certainly one.
只要遵循已发布的 API，就没有任何特殊限制。 围绕它们进行黑客攻击会破坏 Microsoft 支持许可证，在这种情况下，没有任何企业愿意购买您的解决方案。
此外，您应该知道 Office API 是一个充满痛苦的世界。 Office 2007 的效果要好得多（Office 14 附带了很多很酷的东西），但任何比这更旧的东西都只是自找麻烦……话又说回来，这取决于您到底想做什么……
无论如何，你应该看看一些参考项目，比如 SAP 和 Microsoft 联合开发的 Duet (www.duet.com)。 我在我的博客上得到了一些相关信息： http://www.developerzen.com/category /sap/sapduetmendocino/
还有https://www.obacentral.com/default.aspx
There arent any special limitations as long as you follow the published APIs. Hacking around them breaks Microsoft supoort license and no bussiness out there will want to buy your solution in that case.
Furthermore you should know that the Office APIs are a world of pain. Its a lot better with Office 2007 (and there's lots of cool stuff coming with Office 14) but anything older than that is just asking for trouble... then again, depends on what exactly you're trying to do..
In any case, you should check out some reference project like Duet (www.duet.com) jointly developed by SAP and Microsoft. I got some info on that on my blog: http://www.developerzen.com/category/sap/sapduetmendocino/
There's also https://www.obacentral.com/default.aspx