Getting Started
Finbuckle.MultiTenant is designed to be easy to use and follows standard .NET conventions as much as possible. This introduction assumes a standard ASP.NET Core
use case, but any application using .NET dependency injection can work with the library.
Installation
First, install the Finbuckle.MultiTenant.AspNetCore NuGet package:
.NET Core CLI
$ dotnet add package Finbuckle.MultiTenant.AspNetCore
Basic Configuration
Next, in the app's startup ConfigureServices method call AddMultiTenant<T> and its various builder methods:
public void ConfigureServices(IServiceCollection services)
{
...
services.AddMultiTenant<TenantInfo>()
.WithHostStrategy()
.WithConfigurationStore()
...
}
Finally, in the Configure method call UseMultiTenant() to register the middleware:
public void Configure(IApplicationBuilder app)
{
...
app.UseMultiTenant(); // Before UseEndponts
...
app.UseEndpoints(...);
}
That's all that is needed to get going. Let's breakdown each line:
services.AddMultiTenant<TenantInfo>()
This line registers the base services and designates TenantInfo as the class that will hold tenant information at runtime.
The type parameter for AddMultiTenant<T> must be an implementation of ITenantInfo and holds basic information about the tenant such as its name and an identifier. TenantInfo is provided as a basic implementation, but a custom implementation can be used if more properties are needed.
See Core Concepts for more information on ITenantInfo.
.WithHostStrategy()
The line tells the app that our "strategy" to determine the request tenant will be to look at the request host, which defaults to the extracting the subdomain as a tenant identifier.
See Strategies for more information.
.WithConfigurationStore()
This line tells the app that information for all tenants are in the appsettings.json file used for app configuration. If a tenant in the store has the identifier found by the strategy, the tenant will be successfully resolved for the current request.
See Stores for more information.
Finbuckle.MultiTenant comes with a collection of strategies and store types that can be mixed and matched in various ways.
app.UseMultiTenant()
This line configures the middleware which resolves the tenant using the registered strategies, stores, and other settings. Be sure to call it before calling UseEndpoints() and other middleware which will use per-tenant functionality, e.g. UseAuthentication().
Basic Usage
With the services and middleware configured, access information for the current tenant from the TenantInfo property on the MultiTenantContext<T> object accessed from the GetMultiTenantContext<T> extension method:
var tenantInfo = HttpContext.GetMultiTenantContext<TenantInfo>().TenantInfo;
if(tenantInfo != null)
{
var tenantId = tenantInfo.Id;
var identifier = tenantInfo.Identifier;
var name = tenantInfo.Name;
}
The type of the TenantInfo property depends on the type passed when calling AddMultiTenant<T> during configuration. If the current tenant could not be determined then TenantInfo will be null.
The ITenantInfo instance and/or the typed instance are also available directly through dependency injection.
See Configuration and Usage for more information.
Advanced Usage
The library builds on this basic functionality to provide a variety of higher level features. See the documentation for more details:
Samples
A variety of sample projects are available in the samples directory. Be sure to read the information on the index page of each sample and the code comments in the Startup class.
Compiling from Source
From the command line clone the git repository, cd into the new directory, and compile with dotnet build.
$ git clone https://github.com/Finbuckle/Finbuckle.MultiTenant.git
$ cd Finbuckle.MultiTenant
Cloning into 'Finbuckle.MultiTenant'...
<output omitted>
$ cd Finbuckle.MultiTenant
$ dotnet build
Running Unit Tests
Run the unit tests from the command line with dotnet test from the solution directory.
$ dotnet test
