I have released a simple SQL Localization NuGet package which can be used with ASP.NET Core and any database supported by Entity Framework Core. The localization can be used like the default ASP.NET Core localization.

I would be grateful for feedback, new feature requests, pull requests, or ways of improving this package.

DOCUMENTATION NOW HERE:

http://localizationsqllocalizer.readthedocs.io/en/latest/index.html

Features

• Supports any EFCore persistence
• Import, export
• Cache, reset cache
• support for live update
• Configurable keys for localization records
• Default key display possible, if no localization available
• KISS

NuGet | Issues | Code

Examples:

https://github.com/damienbod/AspNetCoreLocalization/tree/master/src/AspNetCoreLocalization

https://github.com/damienbod/AngularLocalizationAspNetCore

https://damienbod.com/2016/07/15/import-export-asp-net-core-localized-data-as-csv/

Basic Usage ASP.NET Core

Add the NuGet package to the project.json file

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

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("Angular2LocalizationAspNetCore")
		)
	);

	// 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

And now it can be used like the default localization.
See Microsoft ASP.NET Core Documentation for Globalization and localization

Add the standard localization configuration to your Startup ConfigureServices method:

services.Configure<RequestLocalizationOptions>(
	options =>
		{
			var supportedCultures = new List<CultureInfo>
			{
				new CultureInfo("en-US"),
				new CultureInfo("de-CH"),
				new CultureInfo("fr-CH"),
				new CultureInfo("it-CH")
			};

			options.DefaultRequestCulture = new RequestCulture(culture: "en-US", uiCulture: "en-US");
			options.SupportedCultures = supportedCultures;
			options.SupportedUICultures = supportedCultures;
		});
		
services.AddMvc()
	.AddViewLocalization()
	.AddDataAnnotationsLocalization();

And also in the configure method:

var locOptions = app.ApplicationServices.GetService<IOptions<RequestLocalizationOptions>>();
            app.UseRequestLocalization(locOptions.Value);

Use like the standard localization.

using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Localization;

namespace AspNet5Localization.Controllers
{
    [Route("api/[controller]")]
    public class AboutController : Controller
    {
        private readonly IStringLocalizer<SharedResource> _localizer;
        private readonly IStringLocalizer<AboutController> _aboutLocalizerizer;

        public AboutController(IStringLocalizer<SharedResource> localizer, IStringLocalizer<AboutController> aboutLocalizerizer)
        {
            _localizer = localizer;
            _aboutLocalizerizer = aboutLocalizerizer;
        }

        [HttpGet]
        public string Get()
        {
            // _localizer["Name"] 
            return _aboutLocalizerizer["AboutTitle"];
        }
    }
}

Release History

Version 1.0.10

• Support for automaically added undefined resources as ong as the culture is supported
• Support for net461

Version 1.0.6

• return default key if localization cannot be found support

Example:

var useTypeFullNames = true;
var useOnlyPropertyNames = false;
var returnOnlyKeyIfNotFound = true;

services.AddSqlLocalization(options => options.UseSettings(
  useTypeFullNames, 
  useOnlyPropertyNames, 
  returnOnlyKeyIfNotFound, 
  false
));

Version 1.0.5

• bugfix context System.InvalidOperationException import, export

Version 1.0.4

• Updated to .NET Core 1.1
• changed the constraint to included the resourceKey for new records

Version 1.0.3

• adding import, export interfaces

Version 1.0.2

• Updated to dotnet RTM

Version 1.0.1

• Added Unique constraint for key, culture
• Fixed type full name cache bug

Version 1.0.0

• Initial release
• Runtime localization updates
• Cache support, reset cache
• ASP.NET DI support
• Supports any Entity Framework Core database

Links:

Microsoft ASP.NET Core Documentation for Globalization and localization