I got a requirement to support multi-lingual for my application. I intended to use the resource files for the website project (resource files are put in App_GlobalResources directory). However, since some classes in the business logic project also contain
messages (e.g: error message, warning message, etc.), I'm going to put the resource files into a separated class library instead.
My question is that is there any comparison about performance between using "website" resource files and "class library" resource file? Is my solution the best in this case? Could you please give me advice?
nguyen190887
Member
18 Points
17 Posts
Performance impact when using resource class library
Aug 24, 2011 03:50 AM|LINK
My application consists of 3 project:
I got a requirement to support multi-lingual for my application. I intended to use the resource files for the website project (resource files are put in App_GlobalResources directory). However, since some classes in the business logic project also contain messages (e.g: error message, warning message, etc.), I'm going to put the resource files into a separated class library instead.
My question is that is there any comparison about performance between using "website" resource files and "class library" resource file? Is my solution the best in this case? Could you please give me advice?
Many Thanks!
</div>HeartattacK
All-Star
55262 Points
5917 Posts
Moderator
MVP
Re: Performance impact when using resource class library
Aug 24, 2011 03:58 AM|LINK
There shouldn't be any considerable loss of performance for putting the resources in a separate assembly.
blog: www.heartysoft.com
twitter: @ashic
nguyen190887
Member
18 Points
17 Posts
Re: Performance impact when using resource class library
Aug 25, 2011 06:28 AM|LINK
You meant there is no performance impact when we put the resources in a separate assembly, right? (Sorry for my bad English)
HeartattacK
All-Star
55262 Points
5917 Posts
Moderator
MVP
Re: Performance impact when using resource class library
Aug 25, 2011 08:02 AM|LINK
Well the assembly will need to be loaded (as with any dll) but I'd say that's quite insignificant.
blog: www.heartysoft.com
twitter: @ashic