NPv.CQS.Infrastructure 2.0.0

NPv.CQS.Infrastructure

Infrastructure for declarative execution of commands and queries in CQS-based applications.
Includes default implementations, Unit of Work executor, and Autofac integration.

✨ Overview

NPv.CQS.Infrastructure provides essential building blocks for executing commands and queries defined using NPv.CQS.Abstractions.

It includes:

• ICommandBuilder and IQueryBuilder for resolving and executing handlers,
• UnitOfWorkCommandExecutor for transactional command execution,
• Autofac module for automatic handler registration by namespace.

This package is intended for the application or composition root layers, where behaviors are wired and executed.

🚨 Breaking Changes in v2.0.0

Starting with v2.0.0, all commands now return a Result (from NPv.Results) instead of being void tasks.

• Before (v1.x):

  public class CreateOrderCommand : ICommand<CreateOrderCommandContext>
  {
      public Task ExecuteAsync(CreateOrderCommandContext context)
      {
          // Domain logic
          return Task.CompletedTask;
      }
  }
  

• After (v2.x):

  public class CreateOrderCommand : ICommand<CreateOrderCommandContext>
  {
      public Task<Result> ExecuteAsync(CreateOrderCommandContext context)
      {
          if (context.Amount <= 0)
              return Task.FromResult(Result.Failure(new Error("Validation.Invalid", "Amount")));
  
          // Domain logic
          return Task.FromResult(Result.Success());
      }
  }
  

ICommandBuilder and ICommandExecutor have been updated to propagate the Result.
UnitOfWorkCommandExecutor now commits the Unit of Work only if the result was successful.

🔧 Key Features

• 📦 Built-in ICommandBuilder and IQueryBuilder implementations
• 📡 Centralized command and query execution via ICommandBuilder and IQueryBuilder
• 🧩 CQSModule for seamless Autofac integration via namespace scanning
• 💼 UnitOfWorkCommandExecutor for wrapping commands in a Unit of Work with automatic commit on success
• 💡 Compatible with all abstractions from NPv.CQS.Abstractions

📦 Installation

dotnet add package NPv.CQS.Infrastructure

🧪 Usage Example

1. Register Autofac Module (in Program.cs)

builder.Host.UseServiceProviderFactory(new AutofacServiceProviderFactory());

builder.Host.ConfigureContainer<ContainerBuilder>(container =>
{
    container.RegisterModule(new CQSModule("YourApp.HandlersNamespace"));
});

2. Execute a Command Declaratively

var result = await _commandExecutor.ExecuteAsync(new CreateOrderCommandContext(orderId, amount));
if (result.IsFailure)
{
    return BadRequest(result.Errors);
}
return Ok();

3. Execute a Query Declaratively

var order = await _queryBuilder.For<Order>().With(new FindById(orderId));

🧩 Components Included

📚 Related Packages

• NPv.CQS.Abstractions – core interfaces and contracts (now v2.0.0 with Result support)
• NPv.Results – lightweight Result pattern implementation
• NPv.Uow.Abstractions – unit of work contract for transactional execution

Author's Note

This library grew out of my long-standing personal interest in structuring and publishing open source packages. Over time, I’ve revisited and refined earlier internal utilities and ideas, giving them a more consistent shape and preparing them for wider reuse. Along the way, I’ve also taken the opportunity to explore how open source distribution and licensing work in the .NET ecosystem.

It’s a small step toward something I’ve always wanted to try — sharing practical, minimal tools that reflect years of learning, experimentation, and refinement.

Hopefully, someone finds it useful.

Nikolai 😛

⚖️ License

MIT — you are free to use this in commercial and open-source software.