Yes, localization working for EPPlus generated Excel files to Azure

It works (will write soon on how to implement localization in general on MVC 4). What I’ve changed on my approach is now the central provider for the names for properties, henceforth, for the field’s display names is the resource provider, which in my case, is in the Azure SQL DB.

Key is to just use [Display(Name={“Key_Name”}] in the case of the data annotations for properties and string myString=LocalizationResourceProvider.Current.GetString(“{Key_Name}”); for getting key value programmatically.

Then, for the generated Excel file, I just assign the myString to the header row: