Does the approach of localization (resource files with names containing the locales they are meant for) works for Silverlight too?? Or is there any other specific measure because multiple resource files would increase the .xap size redundantly??

Secondly, when I added a reference to System.Xml.Linq to my SL app, it dropped multiple localized dlls to the bin directory (one each in folders de, es etc.) I analyzed those dlls with Reflector. They basically just contain localized strings with no code. My first question is this could be done with a .resx file also (as with ASP.NET). Why an assembly is required?? Also, these assemblies appear to be useless as the .xap contains only the main System.Xml.Linq dll. After the client has downloaded the .xap, how come these dlls come into play?? They just seem like lying there good for nothing.

 This link might be helpul.

BTW in our application we generally use xml that contains localized texts and they are hosted in the web site. The application downloads them and show the localized text according to user location or preference. For finding out user location we use web services sometimes that gives location based on IP address.

Please Mark as Answer if this helps you.
Thanks n Regards
~Tanmoy
Blog: http://anothersilverlight.blogspot.com/

Yes the resx model is silverlight loc model aswell. You have two options keep xap size low

1. Load all the application resources for a culture on demand http://wpf-e.spaces.live.com/blog/cns!2B248D261D0E0035!407.entry

2. Load the loc resources as you use a control http://wpf-e.spaces.live.com/blog/cns!2B248D261D0E0035!458.entry