KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
We use resx files to localize our web applications. We usually create local resx files (that map to a specific page) when only one page uses a certain phrase, and a global resx file when more than one page needs the phrase. But the good thing about global resx files is that they are a class, and you can call the phrases like you call properties of a class: Resource.UI.iNotFound So I was thinking - why have local resx files at all? why not use one global resx file for the whole application, and that way avoid runtime errors from calling non-existent phrases? I'm sure there's a good answer for that, I just don't know what it is....
Tags (comma-separated)
Save Edits
Cancel