If I create a new ILocalizationProvider, how do I get DNN to use it? I don't see anything in the web.config for it, unlike many of the other providers.I am moving to 6.2 from 5.6 and need to migrate the custom approach I have used to check resources in a database first before looking in the .resx files. This works fine and was a couple of lines of code to Localize.vb, which, of course, meant a custom dotnetnuke.dll.I see in 6.2 the code I amended is now in a LocalizationProvider. I could simply redo the code change or maybe I could create a new ILocalizationProvider and avoid changing core DNN?

Thanks. I was trying to avoid modifying core (again!).

I must admit, I thought the whole point of providers was to load them in the config so you can replace them with your own? Ah well. next release maybe?

You might be better off modifying the core to load the localization provider from web.config and then use your own provider. Then submit the code to DNN corp for inclusion. Faster than entering it as an enhancement and more likely it will get added to the core.