Why should I use global resources?

Question

in some projects (web application projects) I use global resource files. (Stored in the App_GlobalResources folder)

pro : Really easy to use: for example. in the markup

Property="<%$ Resources:FILENAME, KEY %>" 

Against : - As far as I know, I can’t change the content of resources on the fly. Therefore, if the client calls and tells me to change the line in the French implementation, I need to deploy a new binary. When using SessionMode = "InProc", which can lead to unwanted behavior, such as session loss, etc.

I would prefer to change the line in the XML file to maximize the performance of the application. I think that one could write one own localization class that implements an XML file as a basic data source (using caching, etc.). So the question is, does it have growth potential?

Can someone tell me more pros or minus for using global resource files? (And I'm still listening to suggestions about changing resource files in a running web application;))

So what are the benefits of using global resources?

Edit: I would like to stick with the “built-in” solutions in Visual Studio or the .NET Framework, rather than using a (unknown) third-party library.

Answer 1

Provider model, so you can change the data source. For example, you can save a resource in a database that is better suited for data-driven applications. Because you can edit, cache, install and update them simply. Visit here .

Answer 2

Global resources allow you to localize your web application. You can have a global resource in one language that you need for support, and you don’t have to duplicate aspx files. It will also allow users to switch to the language they want at runtime.

Look here:

Walkthrough: Using Resources for Localization Using ASP.NET
ASP.NET Web Page Resource Overview