Skip to main content
Version: Next

Changelog

The authoritative release history for all RCommon packages is maintained on GitHub Releases.

Full release notes: https://github.com/RCommon-Team/RCommon/releases

Recent Changes​

Modular Composition (Unreleased)​

Added support for calling services.AddRCommon() from multiple modules in the same process. Registrations merge instead of duplicating or throwing on agreement.

Added

  • Modular composition support — services.AddRCommon() can now be called from multiple modules in the same process. Registrations merge instead of duplicating or throwing on agreement. See Modular Composition.
  • New public API: IRCommonBuilder.GetOrAddBuilder<TSubBuilder>(Func<TSubBuilder>) — third-party WithX<T> extensions opt into sub-builder caching.
  • New public API: IRCommonBuilder.GetBootstrapDiagnostics() — retrieve the soft-duplicate report stashed at host startup.
  • New public API: IServiceCollection.IsRCommonInitialized() — true iff AddRCommon() has been called.
  • New internal IHostedService runs the duplicate-descriptor scanner at host startup and emits a single warning on soft duplicates.

Changed

  • AddRCommon() is now idempotent: subsequent calls return the cached IRCommonBuilder.
  • Singleton-style verbs (WithSimpleGuidGenerator, WithSequentialGuidGenerator, WithDateTimeSystem, WithJsonSerialization<T>, WithSmtpEmailServices, WithSendGridEmailServices) are now idempotent on same-type re-registration. Different-type conflicts throw RCommonBuilderException with diagnostic messages.
  • DataStoreFactoryOptions.Register<,> is now idempotent for identical (name, base, concrete) triples. Conflicts (same (name, base) with different concrete) throw UnsupportedDataStoreException (exception type preserved).
  • AddProducer<T> now deduplicates by concrete producer type via descriptor scan — distinct producer types still coexist.
  • All sub-builder WithX<T> extensions route through GetOrAddBuilder<T>; generic constraints tightened to where T : class, ....

Notes

  • Strictly additive public API surface. No method or interface signature removals.
  • No exception types changed on existing APIs.
  • See Examples/Bootstrapping/Examples.Bootstrapping.MultiModule/ for a runnable demonstration.

Blob Storage Abstractions​

Added RCommon.Blobs as a provider-agnostic blob storage abstraction layer, with two concrete implementations:

  • RCommon.Azure.Blobs — Azure Blob Storage implementation
  • RCommon.Amazon.S3Objects — Amazon S3 implementation

Multi-Tenancy Support​

Added complete multi-tenancy infrastructure:

  • RCommon.MultiTenancy — builder abstraction for registering tenancy providers via WithMultiTenancy<T>()
  • RCommon.Finbuckle — Finbuckle.MultiTenant integration, providing FinbuckleTenantIdAccessor<TTenantInfo> that bridges Finbuckle's resolved tenant context to the ITenantIdAccessor consumed by all repositories
  • All persistence providers (EFCoreRepository, DapperRepository, Linq2DbRepository) automatically filter reads by tenant and stamp writes with the current tenant ID when entities implement IMultiTenant

Domain-Driven Design Support​

Added soft delete and multitenancy to the entity layer:

  • ISoftDelete — opt-in interface for logical deletion; repositories set IsDeleted = true and perform an UPDATE instead of a physical DELETE
  • IMultiTenant — opt-in interface for tenant-scoped entities; repositories filter reads and stamp writes automatically
  • SoftDeleteHelper and MultiTenantHelper utility classes for filter expression building and entity stamping
  • EntityNotFoundException for consistent "entity not found" error handling with type and ID context

Repository Soft Delete Extras​

Extended all persistence providers with explicit soft delete and bulk operation support:

  • DeleteAsync(entity, isSoftDelete: bool) overload on all write repositories
  • Automatic !IsDeleted filtering on all read operations for ISoftDelete entities
  • Bulk delete via ExecuteDeleteAsync on EFCoreRepository

Editorconfig and Code Hygiene​

Added .editorconfig to enforce consistent code style across the solution. All public methods and complex code paths now carry XML documentation comments.

Versioning​

RCommon uses MinVer for automatic semantic versioning from git tags. All packages in the solution share the same version number.

Version numbers follow Semantic Versioning:

  • Major (x.0.0) — breaking API changes
  • Minor (0.x.0) — new features, backward-compatible additions
  • Patch (0.0.x) — bug fixes and documentation updates

Pre-release versions (alpha, beta, rc) are tagged accordingly (e.g., v3.0.0-alpha.1).

Release Schedule​

RCommon does not follow a fixed release cadence. Releases are made when meaningful features, bug fixes, or breaking changes are ready. Subscribe to GitHub Releases or watch the repository to be notified of new versions.

Filing Issues​

Found a bug or missing a feature? Please open an issue on GitHub:

RCommonRCommon
© 2026 RCommon Team. All rights reserved