Some time ago, I wrote about an approach for enabling ASP.NET 2.0 localization within a DotNetNuke application. This approach not only required a core modification, but the change introduced a potential breaking change with third party modules. This was clearly unsatisfactory, and the fact that I was unable to fully solve the problem has been vexing me for some time.
As my research on the recently-released Linq to Sql Adapter (currently hosted on CodePlex) wound down, I decided to investigate a new approach to solving the problem. In my opinion, an optimal solution would fulfill the following requirements:
- Require no core changes
- Be side-by-side compatible with the existing DotNetNuke localization services
- Require little configuration by a hosting user
- Allow strongly-typed per-portal and per-culture access to existing global DotNetNuke resources
- Minimal additional in-memory footprint and reasonable performance
- Enable use of the meta:resourcekey attribute in DotNetNuke modules
- Be fully compatibility with third-party modules
I am pleased to announce a preview release of a custom BuildProvider that, to my knowledge, accomplishes all of these goals.
