Your official information source from the .NET Web Development and Tools group at Microsoft.
VS Silverlight beta2 adjusted its build functionalities to support the new Silverlight runtime localization model, which essentially is “one language, one xap”. This article provides the steps to take to build a localized app
Let us say, you want to localize your app for the culture of “ja-jp”. You have created several resource files and you want VS to pack the satellite assemblies into the .xap file.
1. In the solution explorer unload the Silverlight project and edit the project file. There is pre-created tag of “SupportedCultures” in the first property group tag. Fill in the culture value of “ja-jp”, so you get “<SupportedCultures>ja-jp</SupportedCultures>”. Note, you can also fill in a culture list separated by “,” or “;” to support multiple cultures/languages in the same xap file. For example you can fill in a string of “ja-JP;fr-FR”. VS reads this list and only packs related satellite assembly folders.
2. Save the project file, reload it and then build it. You can open the .xap file generated under “Bin\Debug” to check out the content. You can see VS only packs the “ja-jp” folder, but no “ja” folder since it is not in the culture list.
3. If you would like to create a new xap file for a new culture, say “de”, you need to create new build configuration in VS and insert the tag of “<SupportedCultures>de</SupportedCultures>” into the related property group tag in the project file
The project file change looks like,
4. If you have a hosting web project, you are recommended to turn on the “copy to configuration specific folders” through the “Silverlight Applications” tab in web’s property page dialog. Just click the “Change…” button. You can also enable it in the “Add Silverlight Application” wizard when you create a new project. So different .xap files will stay underneath a separate subfolder, and they won’t overwrite each other.
PingBack from http://www.basketballs-sports.info/basketball-chat/?p=1647
What about HEBREW & ARABIC ?
What About Express Support ?
I added blog artical on how to get language binding working based on your post
Sorry wrong link try http://wpf-e.spaces.live.com/blog/cns!2B248D261D0E0035!203.entry
Ok, I can see why MS has gone with one locale per xap, to reduce the xap file size. But surely this should be the choice of the developer! I should be able to choose if I want one locale per xap or accept having a larger xap containing all the locales i wish.
It's bad enough that SL doesn't support dynamic resource dictionaries, so now I am going to have to have a xap per different customer branding of the app multiplied by the number of supported locales!!
talk about support/build script nightmare..
Anyone looking for a working example of this, download
There are some caveats, please read post: http://silverlight.net/forums/p/17678/62357.aspx#62357
As there is on xap per locale, is there a way to define the Source property to point to the correct locale folder path depending on URL Querystring?
I'm pretty novice with asp.net, but as far as I can see property values cannot be dynamic.
sample source updated.
See post here for comments:
If you want multi lang xap then the culture assemebly's must not in culture sub-folders but in the root of the xap itself.
eg add <AssemblyPart Source="SilverlightApplication1.de.resources.dll" /><AssemblyPart Source="SilverlightApplication1.fr.resources.dll" /> into Deployment.Parts section in file Properties\AppManifest.xml
Sample on http://cid-2b248d261d0e0035.skydrive.live.com/self.aspx/Public/SL-Loc.zip
I’ve just finished teaching my first Silverlight Tour training in Montreal, people were very excited