Localization of Farm Solutions in SharePoint 2010
This topic provides some general information about the process of localizing a solution de batterie de serveurs.
Dernière modification : mercredi 2 février 2011
S’applique à : SharePoint Foundation 2010
Notes
For information about localizing a solution en bac à sable (sandbox), see Localisation de solutions en mode bac à sable (sandbox).
Localization and the SharePoint Packaging System
Strictly speaking, a Microsoft SharePoint Foundation solution package (.wsp file) is not a language-relative file. A given solution package can be installed and deployed on any farm regardless of the languages that are being used on the farm.
However, the various components within the solution, including application pages, site definitions (webtemp*.xml files) strings in assemblies, and the various components within Features can all be localized. The process is not fundamentally different from the process of localizing any Microsoft ASP.NET or Windows-based application. You can include localized versions of images, CSS files, .aspx files, and any other files that have localizable content. In almost all scenarios, you will use .resx files for the languages into which you are localizing your solution. These can be deployed globally, for a specific web application, for a specific Feature, or for a specific Web Part.
All of these resources are included in the solution package file and are deployed to the appropriate places when the solution is deployed from a farm's solution store. The Outils de développement SharePoint dans Microsoft Visual Studio 2010 make this a simple process.
For two detailed examples, see Procédure : localisation des colonnes, types de contenu et listes and Procédure pas à pas : localisation d’un composant WebPart.
Localizing a Solution that has Already Been Distributed
Frequently, you must release a SharePoint Foundation solution before it is localized into all the languages you intend. In such cases, one option is to distribute a new version of the solution after support for one or more additional languages is added to it. (For more information about upgrading a solution de batterie de serveurs, see Mise à niveau à partir d’une solution de batterie.) But there is an alternative strategy. You can package the resources for each additional language into its own solution de batterie de serveurs that has the same Solution ID as the original solution but is designated to be a language pack. This language pack solution can then be distributed and farm administrators can install it on farms where the original solution is installed. The effect is that the original solution is localized into the new language. For more information about creating and installing language packs, see Utilisation de solutions de batterie de module linguistique.
Voir aussi
Concepts
Installation et déploiement d'une solution de batterie de serveurs
Utilisation de solutions de batterie de module linguistique