Does DNN 6 support the ASP.NET localization approach? DNN -6 would prevent .resx files from being opened and then a DNN-specific loacalization approach was used. I believe this is historical in that DNN wanted localization a few months before Microsoft released it so the developers rolled thier own and never changed it to be standard.

My custom modules use ASP.NET localization and get resources from a database with a fallback to the standard provider that uses .resx files if the resource isn't available in the database. It would be much better if DNN simply used the localization provider of Microsoft unless, of course, it doesn't work. The old DNN localization approach could simply be another provider.