in some projects (web application projects) I’m using global resource files. (Stored in the App_GlobalResources folder)
pro:
Really easy to use: e.g. in the markup
Property="<%$ Resources:FILENAME, KEY %>"
con:
– As far as I know, I can’t change the content of the resources on the fly. So if a customer is calling and tells me to change a string in the french implementation, I need to deploy a new binary. While using SessionMode=”InProc” that might lead to undesired behaviour, like session loss etc.
I’d rather change a line in an XML file, to ensure maximum uptime of the application. I think It would be possible to write one’s own localization class, that implements an XML file as underlying datasource (using caching etc.). So the question is, is there any upside in doing so?
Can anybody tell me more pros or cons for using global resource files? (And I’m still listening to suggestions to change resource files in a running web application 😉 )
So what benefits do I have by using global resources?
Edit: I’d like to stick to “build-in” solutions in Visual Studio or the .net framework, rather than using a (unknown) 3rd party library.
It’s provider model, so you can change the data source. For instance, you can store the resource on the database which is better for data driven applications. Because, you can edit, cache, install and update them simply. Visit here.