I'm already aware about all the benefits of using resource files when translating an ASP.NET website and implemented it in some projects. But I ended up with some inconveniences:
The optimal structure to organize the different resource files. Trying to find the balance between too many files (e.g., 1 per page) and too few (e.g., 1 for the whole project) taking into account the reuse of tags between pages.
The high number of resulting tags.
Some tags are high bounded to web design and even contain HTML code.
For short text tags it's almost fine but with longer ones having HTML embedded it's a bit chaotic. Using web controls/pages per language instead of multiple tags could be a possibility?
I need to, at least, contemplate an alternative to resource files. If it's not a good option, any recommendation to deal with the above inconveniences?