Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I kept on looking for guidelines, and found this in <a href="http://msdn.microsoft.com/en-us/library/ms227427.aspx" rel="noreferrer">MSDN</a>:</p> <blockquote> <p><strong>Choosing Between Global and Local Resource Files</strong></p> <p>You can use any combination of global and local resource files in the Web application. Generally, you add resources to a global resource file when you want to share the resources between pages. Resources in global resource files are also strongly typed for when you want to access the files programmatically.</p> <p>However, global resource files can become large, if you store all localized resources in them. Global resource files can also be more difficult to manage, if more than one developer is working on different pages but in a single resource file.</p> <p>Local resource files make it easier to manage resources for a single ASP.NET Web page. But you cannot share resources between pages. Additionally, you might create lots of local resource files, if you have many pages that must be localized into many languages. If sites are large with many folders and languages, local resources can quickly expand the number of assemblies in the application domain. </p> <p>When you make a change to a default resource file, either local or global, ASP.NET recompiles the resources and restarts the ASP.NET application. This can affect the overall performance of your site. If you add satellite resource files, it does not cause a recompilation of resources, but the ASP.NET application will restart.</p> </blockquote> <p>So it seems that it's really up to the programming team to weigh the pros and cons of each method and choose what's good for them.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload