entityframework-dotnet-custom-di

What problem does it solve?

When building multi-tenant applications with the Jarvis .NET framework, the default Entity Framework tenant resolution logic may not fit specific business requirements, and modifying the core Jarvis library is prohibited as it breaks update compatibility and long-term maintainability. This Skill provides a supported, non-invasive way to customize tenant ID and connection string resolution without altering Jarvis core code.

Core Features & Use Cases

• Custom Tenant ID Resolution: Implement custom logic to map incoming tenant identifiers (such as tax codes) to valid tenant GUIDs using the ITenantIdResolverFactory and keyed ITenantIdResolver interfaces.
• Custom Connection String Resolution: Override default connection string selection for tenants, for example to route storage operations to MinIO object storage, using keyed ITenantConnectionStringResolver.
• Use Case: A multi-tenant SaaS application that identifies tenants by tax code instead of subdomain, and stores tenant files in MinIO, can use this Skill to implement both custom resolution logic without modifying Jarvis core packages.

Quick Start

Implement custom tenant ID and connection string resolution for your Jarvis Entity Framework multi-tenant application by registering the required resolver services after the core EF setup in your Program.cs file.