Files
Copilot d525bc3f28 Bound reconnect cleanup and organize samples by domain (#4276)
# Description

This PR fixes bounded ManagedSession reconnect cleanup and reorganizes
the sample applications into domain-focused folders.

## Reconnect cleanup

- Bounds reconnect integration cleanup with independent 30-second close
and dispose limits.
- Sends `CloseSession` through the awaited transport request path during
`Session.DisposeAsync`.
- Preserves explicit `Session.CloseAsync` behavior that waits for or
cancels outstanding publish requests.
- Covers the disposal request path with a regression test.

## Sample organization

- `samples/OpenUsd`: `GeneratorServer`, `SiteCompositionServer`
- `samples/Redundancy`: `RedundantClient`, `RedundantServer`,
`RedundantPubSub`
- `samples/Isa95`: `MinimalIsa95Server`
- `samples/MinimalApi`: `MinimalBoilerServer`, `MinimalCalcServer`,
`MinimalClient`
- `samples/DI`: `PumpDeviceIntegrationServer`
- `samples/Lds`: `ConsoleLdsServer`
- `samples/Reference`: `ConsoleReferenceClient`,
`ConsoleReferenceServer`
- `samples/PubSub`: `ConsoleReferencePubSubClient`

`UA.slnx` now exposes the same requested domain groups. Project
references, tests, runtime sample probes, CI workflows, Dockerfiles,
Compose files, helper scripts, and documentation were updated to the new
paths. `samples/Robotics/MinimalRobotServer` remains under `Robotics`.

## Validation

- `dotnet build UA.slnx`
- 3 Redundancy short-haul sample tests
- 70 DI sample tests
- 914 OpenUSD tests
- 1 WotCon model-materialization test
- 137 AOT tests
- `docker compose config` for all 6 moved Redundancy Compose files

## Related Issues

- Fixes #4273

## Checklist

- [ ] I have signed the
[CLA](https://opcfoundation.org/license/cla/ContributorLicenseAgreementv1.0.pdf)
and read the
[CONTRIBUTING](https://github.com/OPCFoundation/UA-.NETStandard/blob/master/CONTRIBUTING.md)
doc.
- [x] I have added tests that prove my fix is effective or that my
feature works and increased code coverage.
- [x] I have added all necessary documentation.
- [x] I have verified that my changes do not introduce new build or
analyzer warnings.
- [x] I built the complete `UA.slnx` solution locally.
- [ ] I ran all tests locally against at least .NET Framework and .NET
10.
- [ ] I fixed all failing and flaky tests in the CI pipelines and all
CodeQL warnings.
- [x] I have addressed all PR feedback received.

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: marcschier <11168470+marcschier@users.noreply.github.com>
Co-authored-by: Marc Schier <mschier@microsoft.com>
Co-authored-by: Marc Schier <marcschier@users.noreply.github.com>
Copilot-Session: a2c2838f-74ae-4997-a1d4-50574d9e0636
2026-08-21 04:35:47 +00:00
..

OPC Foundation UA .NET Standard Minimal Client

Introduction

The minimal console client demonstrates a clean, lightweight OPC UA client implementation using the modern fluent API and dependency injection with HostApplicationBuilder. It is designed as an educational reference and starting point for building OPC UA client applications.

Key Features

  • Fluent DI API: Uses HostApplicationBuilder with fluent .AddOpcUa(), .AddClient(), .AddSubscriptions(), and .AddAlarms() configuration
  • Secure by Default: Discovers a SignAndEncrypt / Basic256Sha256 endpoint unless --insecure is explicitly supplied
  • Managed Sessions: Leverages the modern IManagedSessionFactory for simplified session management
  • Fluent Subscriptions: Creates a V2 subscription and monitored item with AddSubscription() and TryAddMonitoredItem()
  • Dependency Injection: Fully integrated Microsoft.Extensions.DependencyInjection with host-based lifetime management
  • Service-Provided Telemetry: Uses the DI-integrated ITelemetryContext for logging, metrics, and activity tracking
  • Alarms & Conditions: Includes A&C client support via .AddAlarms()
  • Console Logging: Integrated console logging for visibility into client operations
  • Native AOT Compatible: Supports ahead-of-time compilation with .NET

Getting Started

Prerequisites

  • .NET 10.0 SDK or later
  • An OPC UA server accessible at the specified endpoint

Running the Client

To connect to the default MinimalBoilerServer:

dotnet run

The server certificate must already be trusted. For local development only, explicitly opt into automatic trust:

dotnet run -- --auto-accept

To explicitly select an endpoint without message security:

dotnet run -- --insecure

To connect to a different server:

dotnet run -- "opc.tcp://localhost:62542/MinimalCalcServer"

Example Usage

The minimal client demonstrates the following operations:

  1. Host Setup: Creates an application host with Host.CreateApplicationBuilder()
  2. DI Configuration: Configures the application and client services with the fluent API
  3. Endpoint Discovery: Selects the requested secure endpoint through .AddDiscoveryAndConnect(...)
  4. Session Connection: Connects through the DI-provided managed-session factory
  5. Subscriptions: Monitors ServerStatus.CurrentTime with the V2 subscription API
  6. Alarms & Conditions: Resolves AlarmClientFactory and creates an A&C client for the session
  7. Browsing: Browses the server's address space (ObjectsFolder)
  8. Reading: Reads the server's current time from the StandardServer
  9. Clean Shutdown: Properly closes the subscription, session, and host

Architecture

Program.cs

The application uses top-level statements and demonstrates:

  • Configuring application identity and security directly inside .AddClient(...)
  • Setting up HostApplicationBuilder with OPC UA client services
  • Building and validating the ApplicationConfiguration inside the DI infrastructure
  • Configuring services via fluent API: .AddOpcUa().AddClient(...).AddSubscriptions().AddAlarms()
  • Discovering a secure endpoint and connecting through the DI-provided managed-session delegate
  • Creating a V2 subscription and monitored item with the fluent session extensions
  • Resolving AlarmClientFactory for Part 9 Alarms & Conditions operations
  • Performing basic OPC UA operations (Browse, Read)
  • Proper resource cleanup for the subscription, session, and host

DI Container Integration

The client follows the patterns described in DependencyInjection.md:

  • HostApplicationBuilder: Central entry point for DI and host setup
  • Client Options: OpcUaClientOptions exposes the application identity fields (ApplicationName, ApplicationUri, ProductUri, AutoAcceptUntrustedCertificates, etc.) directly alongside managed-session defaults, so a client-only host can configure everything inside .AddClient(...) without a separate configuration construction step
  • Factory Pattern: IManagedSessionFactory for runtime endpoint selection
  • Fluent API: Chainable .AddXxx() methods on IOpcUaBuilder

Educational Value

This minimal client serves as:

  • A clean reference implementation for building OPC UA clients with dependency injection and HostApplicationBuilder
  • A learning resource for understanding the modern OPC UA client stack and fluent DI patterns
  • A template matching the architecture of MinimalBoilerServer for consistency
  • A starting point for custom client applications

For More Information