Re: Whether to use .NET localization support or roll our own...

Our portal is like DotNetNuke..We have modules, dynamically built pages,
library dlls, components. The application itself contains multiple projects.
What would be the best organization of resources files if we go the resource
files route? Each project containning a App_LocalResources, and one
App_GlobalResources at the solution level?

Dr


On Sat, Feb 28, 2009 at 1:22 AM, Dean Cleaver <
[email protected]> wrote:

> I've used databased localisation for years, and it's worked for me -
> however I have several templates for a code generator to deal with the
> mundane code of it - be sure you're prepared for that.
>
> But that aside, it's extremely powerful. And means that each site can be
> customised and menus changed without bugging the developers and having the
> site recompiled and published.
>
> -----Original Message-----
> From: Discussion of advanced .NET topics. [mailto:
> [email protected]] On Behalf Of Dron Regmi
> Sent: Saturday, 28 February 2009 12:31
> To: [email protected]
> Subject: [ADVANCED-DOTNET] Whether to use .NET localization support or roll
> our own...
>
> We are in process of localizing our portal, for Spanish language to start
> with. Wondering if we should use resource assemblies or roll out own
> framework and store all localizable data in sql server...Any tips or
> experiences on this, please...
>
> thanks
>
>  ===================================
> View archives and manage your subscription(s) at
> http://peach.ease.lsoft.com/archives
>
> ===================================
> View archives and manage your subscription(s) at
> http://peach.ease.lsoft.com/archives
>

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives