damienbod
damienbod
Sorry for the slow answer, busy at the day job Hi @abircan yes, you could just use EF Core with a new context, or use the existing to create your...
Hi @inexuscore Seed should be possible as you have the DbContext in your project. If changes are required to the DbContext itself, then I would use the Localization.SqlLocalizer directly instead...
I'll add an interface for the LocalizationModelContext : ILocalizationModelContext Then you can write your own if required, for example configuring a default value for the UpdatedTimestamp column
interface won't work, need to think of a better solution.
http://stackoverflow.com/questions/39556953/asp-net-core-viewmodel-dataannotations-localization
https://github.com/aspnet/Mvc/issues/3518
https://github.com/aspnet/Mvc/pull/5129/files
https://github.com/dotnet/corefx/issues/11846
https://github.com/aspnet/Mvc/pull/5287#pullrequestreview-485632
solution: https://github.com/aspnet/Mvc/issues/2706#issuecomment-248049748