n
n
n
n
nLastnweek I was working with localization in SharePoint and just wanted to sharensome thoughts. We all know that this can be Managed with the Resource files andnat run time we can read the values based on the culture (either UI culture ornyour site’s culture) and reosurce files are kept in the 14 hive of SharePointnServer file system.
n
n
nnn
nInwill not dive in to the details of the how to do localization in SharePoint butnI can point out some references to do this , like thisnpost of John Powell and also thisnMSDN post, explained in excellent way.
n
n
n
nSonfar so good, but when we work with sandbox environment then we cannot accessnthe file system of the server and so puzzle is where and how to keep thisnresource files?
n
nWellnbut that didn’t take too much time to solve as MSDN has already given a veryngood documentation to take on this issue.
n
nHerenis link on how to do this : MSDN – Localizationnin Sandbox environment and thisnpost which is a good pictorial explanation.
n
n
n
nSomenQuick Notes :
n
n
n
nWhatnare satellite assemblies? – Satellite assemblies are thencompiled libraries which contains the localizable resources while creatingnmulti lingual applications. So a satellite assembly per language / culture. –nReference Here
n
n
n
nSonwhere these satellite assemblies are placed in Sandbox solutionsn? – when Sandbox solution with Satellite assembies is deployed then everythingnis packaged as wsp and deployed to sitencollection’s Solutions gallery. Reference Here
n
n