.NET Based OPC UA Client/Server SDK


Keep in mind to built your applications against the correct .NET framework. See Software Requirements and Deploying the Final Application for more information.

Deploying an application built with the OPC UA .NET SDK requires two steps:

  1. Copy the directory containing the built binaries to the target machine;
  2. Run the executable as an Administrator with the ‘/install’ argument.

The latter step will create the certificate, create the Windows Service (if required) and set the file permissions correctly. For servers, the installation process will also open firewall ports; configure HTTP.SYS to allow the application to use HTTP or HTTPS endpoints and bind the machine HTTPS certificate to the ports used by the application.

The configuration file that controls the installation process can be passed as a command line parameter or the information can be stored in the default configuration file for the application.

The install process is described in more detail below.


The following table lists the files that need to be copied for a simple client application:

FullClient.exeThe executable assembly created by the application developer.
UnifiedAutomation.UaClient.dllThe assembly for the Unified Automation .NET Client SDK.
UnifiedAutomation.UaBase.dllThe base assembly for the Unified Automation .NET SDKs.
Opc.Ua.CertificateGenerator.exeA certificate generation utility.
Interop.NetFwTypeLib.dllAn Interop assembly used to access the Windows Firewall APIs.

The Opc.Ua.CertificateGenerator.exe utility is only required for installation. It is not required once an application is configured or if certificates are assigned using some vendor defined mechanism.

If the SDK development environment is installed on a machine the Opc.Ua.CertificateGenerator.exe utility can be found in the “Program Files (x86)” directory under “UnifiedAutomation\UaSdkNetBundleBinary\bin”.