This OPC UA reference implementation is targeting the .NET Standard and is certified for compliance through the OPC Foundation's Certification Test Tool (CTT) V1.03. .Net Standard allows developing apps that run on all common platforms available today, including Linux, iOS, Android (via Xamarin) and Windows 7/8/8.1/10 (including embedded/IoT editions) without requiring platform-specific modifications. Furthermore, cloud applications and services (such as ASP.Net, DNX, Azure Websites, Azure Webjobs, Azure Nano Server and Azure Service Fabric) are also supported. For more information and license terms, see here.

1. Fully ported Core UA stack and SDK (Client, Server, Configuration & Sample assemblies)
2. Sample Servers and Clients, including all required controls, for .Net 4.6.1, .NetCore 2.0 and UWP.
3. X.509 certificate support for client and server authentication
4. SHA512 support
5. Anonymous, username and X.509 certificate user authentication
6. UA-TCP & HTTPS transports (client and server)
7. Folder & OS-level (X509Store) certificate-store support
8. Sessions (including UI support in the samples)
9. Subscriptions (including UI support in the samples)
10. OPC UA Reference Server
11. OPC UA Aggregation Server
12. OPC Classic adapter for OPC UA
13. OPC UA Global Discovery Client and Global Discovery Server
14. OPC UA Certification Test Tool Version 1.03.340.358 compliant

All the tools you need for .Net Standard come with the .Net Core tools. See here for what you need.

All required application certificates for OPC UA are created at the first start of each application in a directory or OS-level certificate store and remain in use until deleted from the store.

By default the self signed certificates are stored in a X509Store called CurrentUser\UA_MachineDefault. The certificates can be viewed or deleted with the Windows Certificate Management Console (certmgr.msc). The trusted, issuer and rejected stores remain in a folder called OPC Foundation\CertificateStores with a root folder which is specified by the environment variable ProgramData. On Windows 7/8/8.1/10 this is usually the invisible folder C:\ProgramData. Note: Since the sample applications in the UA-.Net repository use the same storage and application names as UA-.NetStandard, but create only certificates with hostname localhost, it is recommended to delete all existing certificates in MachineDefault to recreate proper certificates for all sample applications when moving to the UA-.NetStandard repository.

By default the self signed certificates are stored in a X509Store called CurrentUser\UA_MachineDefault. The certificates can be viewed or deleted with the Windows Certificate Management Console (certmgr.msc). The trusted, issuer and rejected stores remain in a folder called OPC Foundation\CertificateStores in the LocalState folder of the installed universal windows package. Deleting the application state also deletes the certificate stores.

The self signed certificates are stored in OPC Foundation/CertificateStores/MachineDefault in each application project folder or in a X509Store called CurrentUser\My, depending on the configuration. For best cross platform support the personal store CurrentUser\My was chosen to support all platforms with the same configuration.

By default all sample applications are configured to register with a Local Discovery Server (LDS). A reference implementation of a LDS for Windows can be downloaded from here. To setup trust with the LDS the certificates need to be exchanged or registration will fail.

1. Open the UA-NetStandard.sln solution file using Visual Studio 2017.
2. Choose a project in the Solution Explorer and set it with a right click as Startup Project.
3. Hit F5 to build and execute the sample.

This section describes how to run the NetCoreConsoleClient and NetCoreConsoleServer sample applications.

Please follow instructions in this article to setup the dotnet command line environment for your platform. As of today .Net Standard 2.0 is required.

1. Once the dotnet command is available, navigate to the root folder in your local copy of the repository and execute dotnet restore UA-NetStandard.sln. This command calls into NuGet to restore the tree of dependencies.

1. Open a command prompt
2. Now navigate to the folder SampleApplications/Samples/NetCoreConsoleServer.
3. To run the server sample type dotnet run. The server is now running and waiting for connections.

1. Open a command prompt
2. Now navigate to the folder SampleApplications/Samples/NetCoreConsoleClient.
3. To execute the sample type dotnet run to connect to the OPC UA console sample server running on the same host. To connect to another OPC UA server specify the server as first argument and type e.g. dotnet run opc.tcp://myserver:51210/UA/SampleServer.
4. On first connection, or after certificates were renewed, the server may have refused the client certificate. Check the server and client folder OPC Foundation\CertificateStores\RejectedCertificates for rejected certificates. To approve a certificate copy it to the OPC Foundation\CertificateStores\UA Applications folder.
5. Retry step 3 to connect using a secure connection.

• Please refer to the OPC Foundation UA .Net Standard Library COM Server Wrapper for a detailed description how to run the OPC COM wrapper.

• Please refer to the OPC Foundation UA .Net Standard Library Aggregation Client and Server for a detailed description how to run the aggregation client and server.

• Please refer to the OPC Foundation UA .Net Standard Library Reference Server for a detailed description how to run the reference server against the UACTT.

The web telemetry sample was removed as there is a much more complete (and better looking!) solution now available here. You can try this new solution, called "Connected Factory", out here.

We strongly encourage community participation and contribution to this project. First, please fork the repository and commit your changes there. Once happy with your changes you can generate a 'pull request'.

You must agree to the contributor license agreement before we can accept your changes. The CLA and "I AGREE" button is automatically displayed when you perform the pull request. You can preview CLA here.