Request best practice for ResourceManager

[Franz]

I know how to use ResourceManager, but I think I don't use it wisely.

I have a web user control. Inside the control, I need to call
ResourceManager.GetString. However, I also need to call
ResourceManager.GetString for my web page body. Therefore, I need to create
2 ResourceManager instances in total. I think it is too big for putting
inside the Session.

I just want to know is there any practice for ResourceManager?

Thanks.
Franz

 

[Teemu Keiski]

Hi,

there is such that you should cache the ResourceManager instance if possible
(per application or per user). That would improve the performance

For example from:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnaspp/html/entloctoolkit.asp

"Caching the ResourceManager greatly improves performance and should be used
regardless of whether the toolkit is used or not."

http://www.theserverside.net/articles/showarticle.tss?id=LocalizationPractices