SilverLight Localization Issue

[Gavin]

I want to localize silverlight application with several different languages.
The normal way is OK to show different languages, just by making several
defferent resource files for each languages. And I found those resouce dlls
shall be packed into the final .xap file. But my case is that Is there any
way not to put the language related dll's into .xap file. just by copying
each resource(zh-cn\XXX.resources.dll) into the ClientBin folder the same
folder as .xap file, for future we may manually add more language resource
dlls without changing the xap file . (Which is like normal winform or asp.net
applicaion does) .I tried this. But can not make it working. Pls advice. I
also have the demo source code. If necessary, I could forward it out.

 

[Gregory A. Beamer]

I want to localize silverlight application with several different
languages. The normal way is OK to show different languages, just by
making several defferent resource files for each languages. And I
found those resouce dlls shall be packed into the final .xap file. But
my case is that Is there any way not to put the language related dll's
into .xap file. just by copying each resource(zh-cn\XXX.resources.dll)
into the ClientBin folder the same folder as .xap file, for future we
may manually add more language resource dlls without changing the xap
file . (Which is like normal winform or asp.net applicaion does) .I
tried this. But can not make it working. Pls advice. I also have the
demo source code. If necessary, I could forward it out.

The issue with Silverlight is it has to follow the web model, which is
stateless. It does, however, have some means of holding state locally,
so it is not completely constrained.

But, it is constrained from reaching across the net to get to the
resource files without some method of getting there.

If you need a completely flexible way of localizing, I would imagine you
could make a call to a "service" that fed the proper resource names. It
would be non-standard, but the call could be made when Silverlight first
stoked up and then held locally on the client machine.

As for ClientBin, I will have to play with that and see if there is some
way to use it for the type of flexibility you desire.

 

[Patrice]

Which version ? My understanding is that this is one of the new fatures
provided by Silverlight 3. Try :

http://timheuer.com/blog/archive/2009/07/13/silverlight-3-cached-assembly-feature.aspx