Understanding OPC Server development using .NET

NET is the choice platform for most client applications and it’s also a good choice for the development of OPC servers.

Server toolkits isolate the OPC specified COM interface and application independent server functionality into a generic server part. The toolkit user only has to implement the application specific server functionality. In .NET server toolkits the generic server part includes a .NET wrapper, allowing the user to implement the application specific server part in .NET, either C# or VB.NET.

Server Toolkit structure
.NET OPC servers need to consist of two parts:

• The generic part with the COM handling and the .NET wrapper
• The application part that is coded in a .NET language such as C# or VB.NET

As with traditional Rapid OPC server toolkits, the generic part can either be implemented as a DLL or as an EXE with the application part in a DLL.

Download the complete whitepaper for all the details.

Author: Advosol

view complete profile

Advosol Inc. is the leading provider of .NET components for the developer of OPC DA, AE, HDA and XML-DA client and server applications. Advosol’s client components are up-to-date with the latest technology. They work in 32-bit and 64-bit systems and are Authenticode signed to ensure quality and to simplify Windows Vista Certification. The server toolkits reduce the OPC server development to a .NET assembly for the ‘device’ access. The OPC system integrator can use our XML DA Gateways and Bridge to eliminate DCOM issues and achieve secure remote access. All Advosol products include extensive documentation and 90 days support.