I am pleased to announce a preview release of a custom BuildProvider that re-enables ASP.NET 2.0 Localization in a DotNetNuke application.  This includes:

• Allowing strongly-typed access to global DotNetNuke resources (e.g.; Resources.GlobalResources.Error_Text)
• Allowing weakly-typed access to resources via a cached ResourceManager object (Resources.GlobalResources.ResourceManager.GetString("Error.Text")
• Both of the above yield localized, portal-specific resource values.
• Enabling use of the meta:resourcekey attribute in modules and usercontrols (e.g.; <asp:Label runat="server" meta:resourcekey="MyResource" />

To my knowledge, there was previously no core-friendly method of realizing the above functionality.

Deployment requires only one small change to the web.config, and works with all commonly-deployed DotNetNuke resource files (the BuildProvider gracefully handles ResX versions 1.3, 2.0, and those files missing valid resheaders).

I am eliciting feedback from the community (especially those non-native English speakers who depend on strong DotNetNuke localization support) for feedback and comments about their experiences with this approach.

Read more at my blog, located here.
Visit the CodePlex project site by clicking here.

Brandon