v4.0.4

Fix for issue #31 by @rrtischler :

• added ExStringLength with min value error message.

v4.0.3

Fix for issue #30

• Removed Required error message from ExRangeAttributeAdapter and ExRegularExpressionAttributeAdapter

v4.0.2

Hotfix for #29 , no changes just a small workaround for implementing custom validation attributes along with Ex validation attributes.

See #29 for the details.

v5.0.0-beta2

A lot of news in this package, contains

• Localization with DB support
• Auto adding missing keys to the db
• Auto translate resource keys via online translation servies
• Simple interface for managing cultures, resources and translations

.net5 support

• Requires preview version of VS2019

LazZiya.ExpressLocalization.DB

• Enable localization with DB support

LazZiya.EFGenericDataManager

• Automatically adding missing resource keys to the database

LazZiya.TranslationServices

• Automatically translating missing localized values using online translation services.
• Ability to extend custom translation services thanks to IXLTranslationService interface.
• Predefined online translation providers (Google, Yandex, MyMemory, SYSTRAN.io)
• Requires RapidApi/Yandex api key to be added to user secrets as described here.

LazZiya.ExpressLocalization.UI

• User interface for managing DB Localization

Sample Project

For all above news see the sample .net5 project already included in the repository.

v4.0.1

• Hotfix for issue #22

v5.0.0-beta1

New

• .net5 support
• DB supported localization

DB Supported Localization

To use databse as a source for locaized values do following steps:

• Add Localization stores to the ApplicationDbCotnext

using LazZiya.ExpressLocalization.DB;

public class ApplicationDbContext : IdentityDbContext
    {
        public ApplicationDbContext(DbContextOptions<ApplicationDbContext> options)
            : base(options)
        {
        }

    // Cultures table will hold the supported cultures entities
    public DbSet<ExpressLocalizationCulture<int>> Cultures { get; set; }

    // All localized resources will be saved in this table
    public DbSet<ExpressLocalizationEntity<int>> LocalizationResources { get; set; }
}

• Add new migration:

add-migration ExpressLocalizationStores

• Apply migration:

update-database

• Add some initial values for Cultures and LocalizationResources tables (do it manually or by seeding the db).
• In startup apply DB localization method:

services.AddRazorPages()
                .AddExpressLocalizationDB<ApplicationDbContext>();

• All the rest is similar to the regular localization steps explained in wiki

• Sample repo: https://github.com/LazZiya/ExpressLocalizationSampleNet5

v4.0

This release contains all changes from v4.0-preview1. See ExpressLocalization wiki for all documentations.

4.0-preview1

New

• Localization TagHelpers are included in LazZiya.ExpressLocalization
• Removed dependency on LazZiya.TagHelpers nuget package, this will break the auto registration and requires manual registration of localization-validation-scripts taghelper component.
• Fix for ExCompare attribute where the other attribute name was not locaized in the error message

Visit LazZiya.ExpressLocalization wiki space for all documentation

3.2.0

Express DataAnnotations that produces locaized error messages by default without providing an error message.

e.g. below attribute will produce a localized validation error if the name is not provided:

[ExRequired]
public string Name { get; set; }

For instruction of use and more details see Express Attributes in the wiki page.

3.1.3

DotNetCore 3.1 support