	Build	Localization.SqlLocalizer
.net core

========================

Documentation: http://localizationsqllocalizer.readthedocs.io/en/latest/

NuGet | Issues | Code

Basic Usage ASP.NET Core

Add the NuGet package to the project.csproj file

"dependencies": {
        "Localization.SqlLocalizer": "3.1.0",

Add the DbContext and use the AddSqlLocalization extension method to add the SQL Localization package.

public void ConfigureServices(IServiceCollection services)
{
    // init database for localization
    var sqlConnectionString = Configuration["DbStringLocalizer:ConnectionString"];

    services.AddDbContext<LocalizationModelContext>(options =>
        options.UseSqlite(
            sqlConnectionString,
            b => b.MigrationsAssembly("ImportExportLocalization")
        ),
        ServiceLifetime.Singleton,
        ServiceLifetime.Singleton
    );

    // Requires that LocalizationModelContext is defined
    services.AddSqlLocalization(options => options.UseTypeFullNames = true);

Create your database

dotnet ef migrations add Localization --context localizationModelContext

dotnet ef database update Localization --context localizationModelContext

========================

ASP.NET Core MVC Localization Example

AspNetCoreLocalization

Commits

Merge pull request #93 from nehio/main

Update Localization.SqlLocalizer.csproj

Update Changelog.md

Merge pull request #88 from suntereo/main

This change enhances fallback behavior so that if there is no "en-US" record in the table but there is "en", it will return "en" instead of not found. This change could further be enhanced by adding a setting to turn on/off.

I would like to make it so that matching LocalizationCulture is case insensitive. If a person managing localization data uses “en-us” instead of “en-US” for a record, it will not be found because the search today is case sensitive. This change makes it case insensitive.

README

ASP.NET Core MVC Localization Example