mirror of https://github.com/OPCFoundation/UA-.NETStandard.git synced 2026-10-19 15:22:15 +08:00

Files

T

Marc Schier 82347dc1da Address PR #3852 review feedback

- Move all channel-related types into `Stack/Opc.Ua.Core/Stack/Client/Channels/`
  subfolder (#13).
- Un-obsolete `SessionReconnectHandler` and the SessionExtensions
  `ReconnectAsync(connection, ct)` / `(channel, ct)` extensions; remove
  all SRH-related `#pragma warning disable CS0618` suppressions from
  applications and tests. AttachChannel/DetachChannel remain obsolete (#1, #4).
- Remove the shared-budget section from MigrationGuide.md (#3).
- Mark `ManagedSession.AttachChannel`/`DetachChannel` `[Obsolete]` so the
  warning surfaces all the way up the supported API surface (#9).
- Break the `<see cref=…>` line in `Session.ChannelManager.cs` to stay under
  140 chars (#10).
- Move `ChannelManagerSessionFactory` from `Opc.Ua.Gds.Client.Common` into
  `Opc.Ua.Client` as a public, documented session-factory option (#11).
- Audit other client classes for `IClientChannelManager`-aware overloads;
  add `ISessionFactory`-accepting overloads on `GlobalDiscoveryServerClient`,
  `LocalDiscoveryServerClient`, `ServerPushConfigurationClient` so any
  session factory (including `ChannelManagerSessionFactory`) works (#12).
- Refactor MCP server (`OpcUaSessionManager`, `Program`) to use
  `ManagedSession` + DI-resolved `IClientChannelManager`; remove
  `SessionReconnectHandler` and manual keep-alive reconnect (#2).
- ConnectionStateMachine code-style fixes: use named delegate types,
  collapse multi-line callback properties to single lines, swap
  `timeProvider`/`maxTotalReconnectTime` constructor param order,
  fix multi-line declaration (#6, #7, #8).
- HTTPS resilience: confirmed `Microsoft.Extensions.Http` and
  `Microsoft.Extensions.Http.Resilience` 10.6.0 support
  `net472`/`net48`/`netstandard2.1`; removed `#if NET8_0_OR_GREATER`
  gating from `ManagedSessionBuilder` and `OpcUaClientBuilderExtensions`
  and HTTPS csproj package refs (#5).

Verification:
- `Opc.Ua.Client` + `Opc.Ua.Core` + `Opc.Ua.Gds.Client.Common` build
  clean (0 warnings, 0 errors).
- 56/56 core channel-manager / retry-budget / HTTPS factory tests pass.
- 129/129 client (ManagedSession + legacy SRH back-compat + SessionExtensions)
  tests pass.

2026-06-05 17:22:41 +02:00

Properties

Update headers and license files (#3388 )

2025-12-04 19:44:40 +01:00

AlarmClientSample.cs

Part 9 Alarms & Conditions: complete server + client implementation (#3805 )

2026-05-29 23:24:53 +02:00

ClientSamples.cs

Enable nullable in Stack, Libraries (9), and Applications projects (#3732 )

2026-05-17 12:55:24 +02:00

ConnectTester.cs

Address PR #3852 review feedback

2026-06-05 17:22:41 +02:00

ConsoleReferenceClient.csproj

Enable nullable in Stack, Libraries (9), and Applications projects (#3732 )

2026-05-17 12:55:24 +02:00

dotnettrace.cmd

Tracing and Logging improvements for the UA Core and libraries (#1631 )

2021-12-16 00:20:08 +01:00

generate_user_certificate.ps1

Secure channel enhancements 2025 11 (Take 3) (#3665 )

2026-04-16 18:56:42 +00:00

Program.cs

Pluggable user-identity provider model (#3807 )

2026-06-02 01:14:54 +02:00

Quickstarts.ReferenceClient.Config.xml

Secure channel enhancements 2025 11 (Take 3) (#3665 )

2026-04-16 18:56:42 +00:00

README.md

Add reverse connect command line support to ConsoleReferenceServer (#3376 )

2025-12-04 15:33:24 +01:00

UAClient.cs

Address PR #3852 review feedback

2026-06-05 17:22:41 +02:00

README.md

OPC Foundation UA .NET Standard Reference Client

Introduction

The console reference client can be configured using several console parameters. Some of these parameters are explained in more detail below.

To see all available parameters call console reference client with the parameter -h.

Reverse Connect

The OPC UA reverse connect feature allows an OPC UA server to initiate the connection to a client, rather than the traditional model where clients connect to servers. This is particularly useful in scenarios where the server is behind a firewall or NAT, making it difficult for clients to directly connect to it.

How to use Reverse Connect

To enable reverse connect mode, specify the client endpoint URL using the --rc or --reverseconnect parameter:

dotnet ConsoleReferenceClient.dll --rc=opc.tcp://localhost:65300 opc.tcp://localhost:62541/Quickstarts/ReferenceServer

The client will start a reverse connect listener on the specified endpoint (e.g., opc.tcp://localhost:65300) and wait for the server to connect to it.

Example: Client and Server with Reverse Connect

Start the client with reverse connect listener on port 65300:

dotnet ConsoleReferenceClient.dll --rc=opc.tcp://localhost:65300 opc.tcp://localhost:62541/Quickstarts/ReferenceServer

In a separate terminal, start the server with reverse connect to the client:
```
dotnet ConsoleReferenceServer.dll --rc=opc.tcp://localhost:65300 -a
```

The server will establish a reverse connection to the client endpoint, and the client will use this connection to communicate with the server.

How to specify User Identity

Username & Password

Specify as console parameters: -un YourUsername -up YourPassword

Certificate

Place your user certificate in the TrustedUserCertificatesStore (the path can be found in the client configuration XML). Make sure to include an accessible private key with the certificate. Specify console parameters: -uc Thumbprint (of the user certificate to select) -ucp Password (of the user certificates private key (optional))