[christopherread]

First v7 increment, part of #84 (design, section 1). Targets the long-running v7 branch.

API

builder.Services.AddObvs(obvs => obvs
    .AddService<IOrderMessage>("orders", service => service
        .UseEndpointProvider(sp => /* any existing transport's IServiceEndpointProvider */)
        .AsServer()));          // or AsClient(); client and server is the default

builder.Services.AddObvs("analytics", obvs => ...);   // separate keyed bus, if ever needed

Behaviour

• One bus: a single singleton resolves as both IServiceBus and IServiceBusClient.
• Created at startup: a hosted service creates the bus when the host starts, so configuration errors stop startup. The container disposes it; stopping the host doesn't.
• Repeated calls: AddObvs called more than once adds to the same bus.
• Roles: AsClient() and AsServer() control which endpoints are created.
• Keyed buses: AddObvs(key, ...) registers a bus resolved with [FromKeyedServices(key)]. Each container gets its own bus, so two hosts in one process don't share one.
• Validation: an invalid configuration throws one ObvsConfigurationException listing every problem with its fix. For example, a service with no transport, or a service name used twice.
• ServiceBus.Dispose() is now safe to call twice. The container tracks the bus behind both of its registrations, so it was being disposed twice, and real transports may not tolerate that.

UseEndpointProvider lets every existing v6 transport work straight away. Each transport's own Use<Transport>() method, with options from configuration, comes in a later increment.

Dependencies

The core Obvs package now references Microsoft.Extensions.DependencyInjection.Abstractions and Microsoft.Extensions.Hosting.Abstractions 10.0.13. Both support net462+ and netstandard2.0, so no targets are dropped.

Tests (written first)

• Obvs.Tests/Hosting/TestAddObvs.cs: 13 tests. 12 were agreed before implementation and all failed with NotImplementedException. ShouldDisposeTheBusOnlyOnce was added during implementation and failed with "Expected 1, Actual 2".
• TestServiceBus.ShouldDisposeEndpointsOnlyOnceWhenDisposedTwice: failed before the Dispose guard.
• All pass now: a clean build of the solution has 0 warnings across net472, netstandard2.0 and net10.0, and all 143 unit tests pass.

Not in this increment

• Transport-specific Use<Transport>() methods and binding options from IConfiguration.
• The per-bus instance ID for broker-side names.
• ILogger and OpenTelemetry (v7: OpenTelemetry tracing and metrics, Microsoft.Extensions.Logging #90).
• Handlers (v7: Handler-based API and awaitable RequestAsync alongside Rx #87).
• The in-memory transport (v7: Obvs.Testing: in-memory transport and test harness #88).
• The no-host ObvsBus.StartAsync builder.

🤖 Generated with Claude Code