If buying a comercial toolkit is an option I've used the Northern Dynamics server toolkit and it worked fine. A toolkit will take away a lot of the issues mentioned in the other questions (or at least you should get support if there's a problem).
They've wrapped the OPC protocol up nicely so it makes it easy to use. See one of my questions here for a type-safe Variant wrapper that I wrote to help with this.
SoftwareToolbox's OPCData.NET (http://www.opcdata.net/) claims to be a 100% Managed code solution for OPC Client. SoftwareToolbox also has some other OPC libraries to help with binding OPC data to forms and web interfaces.
Be careful. I haven't used an OPC API yet that properly conforms to any sort of calling conventions, particularily in the area of freeing memory (COM, as documented, or otherwise). Expect a month of debugging memory leaks.
The Code Project article is from the early days of .NET and may not be the best option today.
Alternatives include OPC Foundation's own .NET API (requires OPC Foundation membership) or several commercial products. OPCconnect.com lists a number of these.
发布评论
评论（5）
如果可以选择购买商业工具包，我已经使用了 Northern Dynamics 服务器工具包 并且效果很好。 工具包将消除其他问题中提到的许多问题（或者至少在出现问题时您应该获得支持）。
他们很好地封装了 OPC 协议，因此易于使用。 请参阅我的问题之一，了解类型安全变体我编写的包装器是为了帮助解决这个问题。
If buying a comercial toolkit is an option I've used the Northern Dynamics server toolkit and it worked fine. A toolkit will take away a lot of the issues mentioned in the other questions (or at least you should get support if there's a problem).
They've wrapped the OPC protocol up nicely so it makes it easy to use. See one of my questions here for a type-safe Variant wrapper that I wrote to help with this.
SoftwareToolbox 的 OPCData.NET (http://www.opcdata.net/) 声称是 100% 托管的OPC 客户端的代码解决方案。 SoftwareToolbox 还具有一些其他 OPC 库，可帮助将 OPC 数据绑定到表单和 Web 界面。
SoftwareToolbox's OPCData.NET (http://www.opcdata.net/) claims to be a 100% Managed code solution for OPC Client. SoftwareToolbox also has some other OPC libraries to help with binding OPC data to forms and web interfaces.
当心。 我还没有使用过正确符合任何类型调用约定的 OPC API，特别是在释放内存领域（COM，如文档所述，或其他）。 预计需要一个月的时间来调试内存泄漏。
Be careful. I haven't used an OPC API yet that properly conforms to any sort of calling conventions, particularily in the area of freeing memory (COM, as documented, or otherwise). Expect a month of debugging memory leaks.
代码项目文章来自 .NET 的早期，可能不是当今的最佳选择。
替代方案包括 OPC 基金会自己的 .NET API（需要 OPC 基金会会员资格）或多个商业产品。 OPCconnect.com 列出了其中的一些。
The Code Project article is from the early days of .NET and may not be the best option today.
Alternatives include OPC Foundation's own .NET API (requires OPC Foundation membership) or several commercial products. OPCconnect.com lists a number of these.
您可以在这里找到一篇好文章和一个库：http://www. codeproject.com/KB/COM/opcdotnet.aspx
You can find a good article and a library to start with here: http://www.codeproject.com/KB/COM/opcdotnet.aspx