Skip to main content
net10.0.NETFramework4.7.2.NETFramework4.8net8.0net9.0.NETStandard2.1

OPC UA PubSub adapters that bind publisher/subscriber/action datasets to an external OPC UA server via a managed client session (Part 14).

Published
Aug 28, 2026
1mo ago
Total Downloads
179
179

Install

dotnet add package OPCFoundation.NetStandard.Opc.Ua.PubSub.Adapter --version 2.0.0-preview.3
ProductVersions
.NET
net10.0net8.0net9.0
.NET Standard
netstandard2.1
Other
.NETFramework4.7.2.NETFramework4.8

README

OPCFoundation.NetStandard.Opc.Ua.PubSub.Adapter

Adapters that bind OPC UA PubSub publisher/subscriber/action datasets to an external OPC UA server through a managed client session (Opc.Ua.Client.ManagedSession).

  • Publisher — reads an external server's nodes and publishes them as PubSub DataSets. Two source modes: cyclic Read calls, or a client Subscription (monitored items) with affinity per WriterGroup (default) or DataSetWriter.
  • Subscriber — writes received PubSub DataSet values back to an external server.
  • Actions — maps inbound PubSub Action requests to external server method calls.

Runtime changes to the PubSub configuration store or named adapter options are hot-reloaded incrementally: unchanged sources, sinks and external-server sessions are reused, while removed datasets/readers release their session references. Action target additions and mapping changes are applied by registering updated handlers; target removal currently requires a host restart because the core PubSub action responder API has no unregister operation.

services.AddOpcUa()
    .AddPubSub(pubsub => pubsub
        .AddPublisher()
        .AddUdpTransport()
        .UseConfigurationFile("pubsub-config.xml")
        .AddServerAsPublisher(options =>
        {
            options.Connection.EndpointUrl = "opc.tcp://plant-server:4840";
            options.ReadMode = ReadMode.Subscription; // or Cyclic
        }));

See docs/PubSub.md for the full guide.

Adoption Assessment

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

This version is marked prerelease. Validate its API and upgrade path before production use.No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.Compatibility metadata lists 6 target frameworks; confirm the exact target used by your application.The published metadata declares 149 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.