## Summary
### Documentation
- Stage the documentation index as a learning path: a first application,
independent client, server, and PubSub paths, then data and services,
companion models, production, advanced integration, and draft or
experimental capabilities.
- Add Getting started (repository samples or NuGet packages), OPC UA
concepts, Your first information model, and a production readiness
checklist.
- Add Native AOT application publishing, a first PubSub publisher and
subscriber exchange, and the UDP transport options.
- Add or expand contents navigation throughout `docs/`, and keep
contributor documentation separate.
- Correct outdated SDK examples and capability guidance, consolidate
repeated explanations into canonical guides, and repair local links and
heading structure.
- Rewrite What's New in 2.0 as a concise feature overview with short
linked details; keep migration instructions in the Migration Guide.
- Expand the feature catalogue with specification IDs, GDS, LDS, the OPC
10000-21 onboarding registrar, ISA-95, xRegistry, OpenUSD, and
sample-local models; distinguish draft status, explain crypto
pluggability, and bring performance guidance forward.
- Address review feedback on wording, active monitored items during
shadow reload, and the `Samples.md` filename and references.
- Regenerate the `opcua-v20-migration` plugin's bundled copy of the
migration guides so it matches the edited `docs/migrate/2.0.x` guides.
- Merge the latest `master`, preserving upstream resource-isolation
guidance within the task-based documentation index.
- Retain deferred Lingity findings where appropriate; this PR does not
claim that every document meets the Lingity score thresholds.
### Fixes found while verifying the guides
Each fix has regression tests that fail without it.
- **Client:** V2 subscriptions compared their lifetime with the
operation timeout instead of the session timeout, and logged a spurious
warning. `ISubscriptionEngineContext`, which is new in 2.0, gains a
`SessionTimeout` property; implementations must add it.
- **PubSub:** a subscriber now registers the `DataSetMetaData`
configured on its readers (OPC 10000-14 6.2.9.4), and the UADP decoder
decodes DataSetMessages that carry no ConfigurationVersion. Before, a
secured subscriber of the reference sample received no DataSets.
- **Source generator:** a ModelDesign method that declares its arguments
inline, without a method type, produced code that did not compile; it
now uses `MethodState`. The generated code of existing models is
unchanged.
- **MinimalClient sample:** waits for its first data-change notification
before it disconnects.
### Known issues, not addressed here
- UDP multicast: the publisher does not send on the interface that the
subscriber joins, and `MulticastLoopback` defaults to false. The PubSub
guide uses unicast for the exchange on one computer.
- The UDP metadata announcement is sent unsecured on secured writer
groups; a secured subscriber drops it with a warning.
- A server does not start in globalization-invariant mode, because
`ResourceManager` creates `CultureInfo("en-US")`. The Native AOT guide
cautions against the mode.
## Validation
- `git diff --check` and
`./.azurepipelines/validate-migration-plugin.ps1` (15 bundled migration
docs validated, plugin manifests synchronized).
- Local Markdown links, anchors, file-link casing, and contents lists
checked across all 87 documents under `docs/`. The index links every
top-level guide and every target of the previous index.
- Both Getting started routes, Your first information model, the PubSub
exchange, and the Native AOT publish of the Getting started client and
server were run as documented. The NuGet route and the tutorial use the
public `2.0.0-preview.5` packages.
- The changed libraries build for all target frameworks in Release
without warnings.
- Tests on .NET 10: Opc.Ua.SourceGeneration.Tests 199 passed;
Opc.Ua.SourceGeneration.Core.Tests 3,977 passed, 8 skipped;
Opc.Ua.Server.Tests `Fluent` category 621 passed; Opc.Ua.Client.Tests
subscription-engine tests 70 passed; Opc.Ua.PubSub.Tests 1,374 passed, 2
skipped; PubSub fuzz replay 145 passed. The new and affected tests also
pass on .NET Framework 4.8.
- Earlier merge validation: 174 resource-isolation tests passed on .NET
10.
- The full solution suite was not run locally.
Review and validation artifacts are maintained outside the repository.
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
7.2 KiB
Time and Timer Abstraction (TimeProvider)
When to read this: Read this when adopting
System.TimeProvideracross the stack (replacing directDateTime.UtcNow,Timer, and similar timing primitives in custom NodeManagers, durable subscriptions, and reconnect policies).
Contents
Adopting TimeProvider
Not source-breaking. The stack now uses
System.TimeProvider as
its canonical clock and scheduler so that timeouts, intervals, keep-alive loops,
reconnect back-off, publishing pacing, certificate-lifetime checks, and similar
duration-sensitive code paths are mockable in tests and immune to wall-clock changes.
HiResClock is still in place but every public member is now marked
[Obsolete]. The class itself is not obsolete so that existing field references
(HiResClock.Disabled) keep round-tripping through configuration; only the static
clock-reading members raise CS0618. The recommended replacements are:
| Legacy API | Replacement |
|---|---|
HiResClock.UtcNow |
timeProvider.GetUtcNow().UtcDateTime |
HiResClock.TickCount64 / .Ticks |
timeProvider.GetTimestamp() |
HiResClock.TickCount (int wraparound) |
timeProvider.GetTickCount() (internal extension in Opc.Ua) |
HiResClock.UtcTickCount(offsetMs) |
timeProvider.GetTimestampMilliseconds() + offsetMs |
elapsed-time math via TickCount |
long start = timeProvider.GetTimestamp(); … TimeSpan elapsed = timeProvider.GetElapsedTime(start); |
new Stopwatch() / Stopwatch.StartNew() for duration |
long start = timeProvider.GetTimestamp(); … timeProvider.GetElapsedTime(start); |
new System.Threading.Timer(…) |
ITimer timer = timeProvider.CreateTimer(callback, state, dueTime, period); |
Task.Delay(delay, ct) in production timing loops |
Task.Delay(delay, timeProvider, ct) |
new CancellationTokenSource(timeout) |
new CancellationTokenSource(timeout, timeProvider) |
Constructor pattern. Components that need a clock now take a nullable
TimeProvider as the last constructor parameter with a default value of null.
If null is passed, TimeProvider.System is used. Example:
public sealed class Foo
{
private readonly TimeProvider m_timeProvider;
public Foo(/* existing args */, TimeProvider? timeProvider = null)
{
// existing initialisation…
m_timeProvider = timeProvider ?? TimeProvider.System;
}
}
For published public types whose existing constructors must remain
binary-compatible, the original constructor signature is preserved and a new
overload that ends with TimeProvider? is added. The legacy constructor delegates
to the new one passing timeProvider: null. No existing constructor is marked
[Obsolete] in this release.
Dependency injection. AddOpcUaServerBuilder / AddOpcUaClientBuilder register
TimeProvider.System via TryAddSingleton<TimeProvider> and wire the resolved
provider into every component they construct. To run a server or client against a
fake clock in tests, register a Microsoft.Extensions.Time.Testing.FakeTimeProvider
in the service collection before the OPC UA builders.
services.AddSingleton<TimeProvider>(new FakeTimeProvider());
services.AddOpcUaServerBuilder(/* … */);
Outside DI, pass the TimeProvider directly to the type's constructor as the last
argument.
Migrating off HiResClock. Replace the call with the table above. If the
migration cannot happen immediately, wrap the affected scope with
#pragma warning disable CS0618 / #pragma warning restore CS0618.
// before:
long start = HiResClock.TickCount64;
DoWork();
TimeSpan elapsed = TimeSpan.FromTicks(HiResClock.TickCount64 - start);
// after:
long start = m_timeProvider.GetTimestamp();
DoWork();
TimeSpan elapsed = m_timeProvider.GetElapsedTime(start);
// before:
DateTime utcNow = HiResClock.UtcNow;
// after — when a wall-clock value is required (e.g. for an OPC UA SourceTimestamp):
DateTime utcNow = m_timeProvider.GetUtcNow().UtcDateTime;
// before:
m_timer = new Timer(OnTick, state: null, dueTime: 1_000, period: Timeout.Infinite);
// after:
m_timer = m_timeProvider.CreateTimer(OnTick, state: null,
dueTime: TimeSpan.FromMilliseconds(1_000), period: Timeout.InfiniteTimeSpan);
The Timer field type changes from System.Threading.Timer to ITimer — both
implement IDisposable and the same Change / Dispose semantics; only the
parameter types on Change differ (TimeSpan instead of int/uint/long).
Monotonic timestamps for duration calculations
TimeProvider.GetTimestamp() returns a long monotonic timestamp that does not
suffer from the 32-bit wraparound of Environment.TickCount / HiResClock.TickCount
nor the system-clock drift of DateTime.UtcNow. All internal duration math in the
stack now uses GetTimestamp() + GetElapsedTime(start) instead of int-tick
subtraction. The following public surface changes were made:
Old (removed or [Obsolete]) |
New |
|---|---|
ISession.LastKeepAliveTickCount: int (was on the interface) |
ISession.LastKeepAliveTimestamp: long + timeProvider.GetElapsedTime(timestamp) (legacy int now an [Obsolete] extension property in SessionObsolete) |
ChannelToken.Expired, ChannelToken.ActivationRequired, ChannelToken.CreatedAtTickCount |
Removed. Use ChannelToken.IsExpired(TimeProvider) / ChannelToken.IsActivationRequired(TimeProvider) (internal). |
UaSCUaBinaryChannel.LastActiveTickCount: int (protected) |
Removed. Use UaSCUaBinaryChannel.GetElapsedSinceLastActive(): TimeSpan (internal). |
Pattern for new code computing an internal duration:
// before:
int startTicks = m_timeProvider.GetTickCount();
// ... do work ...
int elapsedMs = m_timeProvider.GetTickCount() - startTicks;
// after:
long startTimestamp = m_timeProvider.GetTimestamp();
// ... do work ...
TimeSpan elapsed = m_timeProvider.GetElapsedTime(startTimestamp);
See also
- Related: sessions-subscriptions.md, node-states.md.
- 2.0 migration index — analyzer quick-start + symptom → sub-doc table.
- Migration Guide — landing page across versions.