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

OPC UA xRegistry generic registry client: resolve a resource by its content-derived id (Opaque NodeId fast path) and register a resource via the CreateResource/Write/Close lifecycle.

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

Install

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

README

Opc.Ua.XRegistry.Client

The generic xRegistry registry client for OPC UA, built entirely on the source-generated ObjectType proxies. It talks to a registry hosted in an OPC UA server address space:

  • Resolve a resource from its content-derived id through the Opaque-NodeId fast path — a read of the node whose Identifier is the raw content-id bytes (no Browse, no fingerprint recomputation). The read is range-based, so a document larger than the session's MaxByteStringLength is fetched in slices rather than failing.
  • Register a resource through the model's own lifecycle — CreateGroup / GetOrCreateGroup, CreateResource / GetOrCreateResource, and the FileType methods ResourceType inherits — plus Delete(ExpectedEpoch) for optimistic concurrency.

XRegistryClient is an abstract base carrying the xRegistry-level API; GenericXRegistryClient is the sealed implementation for any registry namespace. A concrete registry client (for example a schema registry client) derives from XRegistryClient and adds domain-specific naming and defaults; because a domain model subtypes the base types, the generated proxy chain mirrors the OPC UA hierarchy automatically.

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 143 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.