Skip to content

valdisiljuconoks/localization-provider-aspnet

Repository files navigation

LocalizationProvider for Asp.Net

Database driven localization provider for .Net Core applications.

Supporting LocalizationProvider

If you find this library useful, cup of coffee would be awesome! You can support further development of the library via Paypal.

What is the LocalizationProvider project?

LocalizationProvider project is Asp.Net Mvc web application localization provider on steriods.

Giving you main following features:

  • Database driven localization provider for .Net applications
  • Easy resource registrations via code
  • Supports hierarchical resource organization (with help of child classes)

What's new in v6?

Please refer to this post to read more about new features in v6.

Breaking Changes

  • Mapping of the AdminUI has changed.

Old code:

public class Startup
{
    public void Configuration(IAppBuilder app)
    {
        ...
        app.Map("/localization-admin",
                b => b.UseDbLocalizationProviderAdminUI(_ =>
                {
                    _.ShowInvariantCulture = true;
                    ...
                }));
    }
}

Should be changed to:

public class Startup
{
    public void Configuration(IAppBuilder app)
    {
        ...
        app.UseDbLocalizationProviderAdminUI(
            "/localization-admin",
            _ =>
            {
                _.ShowInvariantCulture = true;
                ...
            });
    }
}

Project Structure

Database localization provider is split into main abstraction projects and Asp.Net support project (this).

Getting Started

GitHub Source Code Structure

Asp.Net support project has its own repo while main abstraction projects are included as submodules here.

How to Contribute

It's super cool if you read this section and are interesed how to help the library. Forking and playing around sample application is the fastest way to understand how localization provider is working and how to get started.

Forking and cloning repo is first step you do. Keep in mind that provider is split into couple repositories to keep thigns separated. Additional repos are pulled in as submodules. If you Git client does not support automatic checkout of the submodules, just execute this command at the root of the checkout directory:

git clone --recurse-submodules git://github.com/...

More Info