The OPCAE.NET-UA option extends OPCAE.NET with support for accessing Express Interface (OPC UA) servers.
EUAsting OPCAE.NET client application can be upgraded with UA support by simply compiling the application with a reference to the UA version of the OPCAE.NET DLL. No code changes are necessary.
New client applications can support access to OPC AE and OPC UA servers without additional development effort.
![]() |
The OPCAE.NET-UA solution has important advantages over solutions with an external UA wrapper. DCOM is completely eliminated because the UA wrapping happens within the client application process.
The client application uses only one API, the well established OPCAE.NET API with an extensive set of classes for the efficient development of high quality applications. The different classes such as Visual Studio Designer Components, DataBind and Background Server Access works with OPC AE and OPC UA servers. |
Requirements:
- OPCAE.NET V9.1 or newer
- .NET Framework V4.x
- WCF (Windows Communication Foundation) installed and activated.
Upgrade an existing OPCAE.NET based client application to UA support
The client application needs to be recompiled with references to the UA version OPCAE.NET DLLs. Only these DLLs contain the hooks for UA option DLL.
The DLLs that need to be referenced for DA/UA support are:
- OpcAeNetUA.DLL / OpcAeNetUA.Net4.dll
or OpcAeNetUAWpfUA.dll for WPF applications
- OpcNetBase.dll and OpcNetBaseNet4.dll
The common classes for OPCAE.NET, OPCHDA.NET and OPCAE.NET
- OpcAeNetUAOption.dll / OpcAeNetUAOption.Net4.dll
This is the UA wrapper. It has to be purchased as a license separate from OPCAE.NET
For access to OPC AE servers nothing has changed.
To access UA servers the UA server URL is specified in place of the OPC AE ProgID.
The format is: UA:[scheme://]host/name e.g. UA:opc.tcp://localhost/UAPlus
For details see chapter Communication Configuration.
Create a New OPC AE / UA Application
For Windows Forms applications use the Advosol/opcaenetUA template in the Visual Studio New Project wizard. This creates a solution with the required DLL references.
For other types of applications the references can be added as listed above after the project is created.
Visual Studio 2010/2012/2013/2015/2017 can be used to create application for .NET4.x