QC OTAClient dll
我们通过引用 OTACLient.dll 为使用 OTA API 的客户端之一开发了 QC 适配器。
该 DLL 可重新分发吗?
We have developed a QC Adapter for one of the clients using OTA API by referencing OTACLient.dll
Is this DLL redistributable?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
TDAPIOLELib.dll
可以使用TlbImp.exe OTAClient.dll
生成(使用正确的路径),因此恕我直言,任何重新分发问题都应该与OTAClient.dll
相关。代码>.OTOH
OTAClient.dll
它是 HP ALM 客户端注册(来自加载项页面)的一部分,因此它可以简化部署:当然,我希望
OTAClient.dll
和任何其他客户端组件仅可合法用于 HP ALM 的许可客户端 - 仍在搜索此主题以及使用此主题的自定义应用程序的许可证计数影响dll。TDAPIOLELib.dll
can be generated usingTlbImp.exe OTAClient.dll
(with the correct paths), so IMHO any redistribution concerns should be aboutOTAClient.dll
.OTOH
OTAClient.dll
it's part of the HP ALM Client Registration (from the add-in page), so it might ease the deployment:Of course, I expect that
OTAClient.dll
and any other client components are legal to use only for licensed clients of HP ALM - still searching on this topic and about the licence count influence of the custom apps using this dll.我从未阅读过OTA API提供的EULA,这是我个人的看法;但直觉上我会说这不应该是一个问题。
只要您仅分发您自己的二进制文件,而不是 HP 拥有的二进制文件。
I have never read the EULA provided with OTA API, and this is my own personal opinion; but as a hunch I would say it is not supposed to be a problem.
As long as you distribute only your own binaries and non of those owned by HP.