Folks,

I've been trying to use .NET 2.0 localization in my DNN 4.0.2 project to no avail.  I get null reference exceptions galore when trying to use local or global resources with any of these valid and supported methhods:
http://www.asp.net/QuickStart/aspnet/doc/localization/localization.aspx

I cannot get Strong Typed localization working at all.  the Resources Namespace does NOT show up.  And I believe this is because when I compile, the resource objects cannot be built due to errors in the way DNN has structured its resources  (such as  .Text not being valid in global resources)

May this is not new news?  DNN porting to .NET 2.0 framework known issue?  Or if it is working for other people, I'd sure like to know what the trick is.

Yes, Thanks.  I am aware of the scheme DNN uses for localization.  I like it, I use it.  What I am trying to point out in this thread I suppose is the fact that in should "extend" the dot net framework, not replace or break it.  I should be able to use .NET 2.0 and DNN localization schemes.  I suspect this is simply a matter of DNN 4x being an initial port from .NET 1.1 (DNN 3x) that is not cleaned up and streamlined for .NET 2.0 yet.  On that topic, I think there are vast amounts of DNN 4x that need revisit to utilize .NET 2.0 more efficiently, but that is beyond the scope of this thread. 

The fact stands that DNN 4x breaks .NET 2.0 localization scheme, rather than expand on it, so far as I can see currently with DNN 4.0.2.

Of cause, DNN localization is older than ASP.Net 2.0 and currently DNN 3.2 and DNN 4.0 share the same code base, have the same functions and interfaces - and this shall remain until developement of DNN 3 is retired. But even after this New ASP.net 2.0 features will only be implemented, if their usage brings more advantages than disadvantages. So any extension will need to fully support all current language packs and bring new opportunities for localization. Today developers have one individual resource files per ascx and a shared one per module. Currently there is a strong developement need for content localization - and I would like to see the core team to focus on this feature.

Just my 2 cents.