Substantive.AspNetCore.MultiTenant 9.17.24-build20260204r1

This package provides a standardized way to configure Finbuckle.MultiTenant for ASP.NET Core applications, with first-class support for Razor Pages, multiple tenant stores, and pluggable tenant resolution strategies.

A. Installation

1. Install the package

Install the package via NuGet or update directly in the .csproj file.

<PackageReference Include="Substantive.AspNetCore.MultiTenant" Version="1.*" />

2. Add configuration

Add the configuration below to the appsettings.json or to the configuration provider you are using.

Configure MultiTenantOptions using appsettings.json (or any other configuration provider).

Key settings:

• Strategy – Tenant resolution strategy (Header, Route, or Host)
• TenantStrategyParameter – Header name, route parameter, or host token depending on the strategy
• EndpointTemplate – Required only for HTTP remote store
• DefaultTenantInfo – Optional fallback tenant (not recommended for production)

{
   "MultiTenantOptions": {
     "Strategy": "Route",
     "TenantStrategyParameter": "tenant",
     "EndpointTemplate": "https://tenants.example.com/api/tenants/{tenantId}",
     "DefaultTenantInfo": {
       "Id": "00000000-0000-0000-0000-000000000001",
       "Identifier": "default",
       "Name": "Default Tenant"
     }
   }
}

3. Configure services

Configure the service and configuration into the service collection.

Bind options and register the appropriate tenant store.

Razor Pages (recommended)

builder.Services.AddMultiTenantWithEFCoreStore<TenantStoreDbContext, TenantInfo>(options =>
{
    builder.Configuration.GetSection(nameof(MultiTenantOptions)).Bind(options);
});

B. Choosing the correct store

C. Tenant resolution strategies

D. Usage

B. Usages

Inject ITenantInfo or IMultiTenantContextAccessor<TenantInfo> where needed.

private readonly ITenantInfo tenant;

public IndexModel(ITenantInfo tenant)
{
    this.tenant = tenant;
}

E. Notes and best practices

• Avoid DefaultTenantInfo in production environments
• Do not register multiple tenant stores in the same application
• Centralize tenant lifecycle management when using the HTTP remote store