Genocs.Messaging

Genocs.Messaging — Agent Reference Documentation

Consumer Mode for Agents #

• Assume package is installed from NuGet.
• Do not rely on repository source code access.
• Prefer stable public APIs and extension methods documented here.
• If behavior is uncertain, fail safely and request config/package version details.

Purpose #

Genocs.Messaging defines transport-agnostic messaging contracts and CQRS bridge helpers that are implemented by concrete transport providers.

Quick Facts #

Install #

dotnet add package Genocs.Messaging

Minimal Integration Recipe (Program.cs) #

using Genocs.Core.Builders;
using Genocs.Messaging.CQRS;

var builder = WebApplication.CreateBuilder(args);

IGenocsBuilder gnxBuilder = builder.AddGenocs();

gnxBuilder
    .AddServiceBusCommandDispatcher()
    .AddServiceBusEventDispatcher();

gnxBuilder.Build();

var app = builder.Build();
app.Run();

Configuration #

Genocs.Messaging does not define its own section.

Configuration is supplied by the concrete transport you install:

The base package only contributes contracts and CQRS bridge helpers. If messaging behavior needs to change through configuration, change the installed provider package rather than this package.

Decision Matrix For Agents #

Behavior Notes / Constraints #

• This package does not provide a broker client by itself.
• Subscriber helper methods resolve handlers inside a per-message DI scope.
• CQRS extensions are thin wrappers around the bus publisher/subscriber contracts.

Public Capability Map #

• Publish contract: IBusPublisher.
• Subscribe contract: IBusSubscriber.
• CQRS publish/subscribe helpers in Genocs.Messaging.CQRS.
• CQRS dispatcher bridge registrations for command and event dispatchers.

Dependencies #

• Genocs.Core
• Transport package at runtime (for example RabbitMQ provider)

Troubleshooting #

1. Publish calls succeed but nothing reaches infrastructure. Fix: Install and configure a concrete transport provider package.
2. Handler subscriptions never run. Fix: Register transport subscriber startup flow and call SubscribeCommand<T>() or SubscribeEvent<T>() for each message type.
3. Command/event dispatch is not routed to bus. Fix: Register AddServiceBusCommandDispatcher() and AddServiceBusEventDispatcher() during startup.