Thanks. Right now we get an IStringLocalizer instance but GetAllStrings() returns an empty collection. Would this work in a web forms scenario as well, e.g. when constructor injection is not available should we be able to resolve manually using Litium IoC.Resolve()?
Is there any documentation on this on docs.litium.com?
When creating the resource files it is important the folder they are in. If you wan’t to register the resources as “System strings” you should name the folder as “General”, otherwise the folder name is the same as the module name.
Sorry, but I can’t get this to work. There are no system strings or module strings created no matter which folder I place resource files in. And about the IStringLocalizer, should it work in a ASP.NET 4.6.1 web application? Any other ideas on what we’re missing?
It would be really helpful with some documentation on this.
@hans Can you give us little more info about what you have done with some code snippet where you try to use them and maybe an image over the folder structure and the file names that you using?
The strings is readed at runtime and as fast they are changed in the resx-file they are updated. They are not stored in database.
The folder structure that the files are using reflected the “old” modules and we have one file for each module. When we started with the new BO UI we decided to only have one file and that is loaded from Administration folder. Example on folder names for the CMS/ECommerce is for ModuleCMS and ModuleECommerce.
The accelerator templates in Litium 7 have all their strings in the administrations-folder, even that the entity is for different types.