Hi Walt,

This behavior is by design.  DNN uses its own resource system that is not particularly side-by-side compatible with the ASP.NET 2.0 localization system. 

The reason you are not seeing localization via meta:resourcekey is that the compilation of your resource files is being explicitly disabled at the web.config level.

I blog here a bit about a method that allows one to operate ASP.NET 2.0 localization alongside the existing DNN system.  I do not, however, recommend it in very many situations, so proceed with caution.

Brandon

Hi Walt,

Keep in mind that, because of the way .NET links static constants, this approach risks breaking third-party modules that depend on the value of Localization.ApplicationResourceDirectory.  While I am not aware of any such module (most seem to simply use the public Localization class methods), I also use very few third-party modules.

The DNN team does not have the luxury of being so narrowly focused.  Because they are responsible for supporting a broad ecosystem, such breaking-change issues are of heightened significance.  As such, I would not expect any modifications to the DNN localization system until a "breaking change" version is rolled out.  DNN 5.0 is not such a version.

Brandon