Re: Whether to use .NET localization support or roll our own...
Dave Jones <[email protected]> Sat, 28 Feb 2009 09:50:31 +0000
| Newsgroups | gmane.comp.windows.devel.dotnet.advanced |
|---|---|
| Message-ID | <1602468905-1235814665-cardhu_decombobulator_blackberry.rim.net-1019457777-@bxe1015.bisx.produk.on.blackberry> |
If your going to be supporting more than just English Spanish French and German all strings need to be stored as nvarchars. I would have been with dino up until vs 2008 resources are much eaiser now Dave Dave Jones -----Original Message----- From: Dean Cleaver <[email protected]> Date: Sat, 28 Feb 2009 22:22:55 To: <[email protected]> Subject: Re: [ADVANCED-DOTNET] Whether to use .NET localization support or roll our own... 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