User845932231 posted
1. Divide common resources into logical units and put in App_Globalresources folder. Use them commonly for all the pages. For example create a resx file Messages.resx for all the error and success messages you show in different pages. Create another global
resource file for all UI elements such as Save, Print, Reset buttons, menus etc. (By common message what i mean is a resource that can come in more than one page.)
Now for individual files create Local resources (so for 400 pages, 400 seperate local resources files)and put the resources in that. Whenever you see some text is repeating in another page also, try moving it to global resources.
2. As far as I know the length of the file is not an issue. But if its tooooo huge, managing it will be a bigh issue.
3. No, we havent faced any performnace probs using resource files. It will definitely use more memory than showing text directly from page, but that can be ignorable.
4. For all the Local resource files the name shld be same as the aspx file name..its mandatory.. For global resources you can give what ever name you want.. We usually give file names that can reflect the content of the file.. like Messages.resx, UI.resx
etc
http://wiki.asp.net/page.aspx/55/internationalization/
