Walkthrough: Localizing an Intermediate Declarative Outlook Solution to Another Language
Published: July 2010
This walkthrough shows how to localize an intermediate declarative Microsoft Outlook solution to another language.
Typically, you first create a declarative solution for your language, then localize the solution into other languages so that it can be used by users in other countries or regions. Use this walkthrough to learn how to implement the same solution for multiple locales.
Before proceeding with this walkthrough, be aware of the following:
This walkthrough is based on the AdventureWorks2008 Declarative Outlook Solution Sample that is provided in the Microsoft SharePoint 2010 Software Development Kit (SDK), and shows how to localize the files in this sample. You can apply the steps in this walkthrough to localize your own declarative Outlook solution.
This walkthrough shows how to localize the user interface (UI) for the Outlook solution. It does not localize the sample data provided by the sample database that the solution uses.
For each language that you want to localize the solution into, you must have a separate installation file. For example, to localize your solution into five languages, you must have five installation files, one for each language. If you make a change to one file, you must make that same change to each separate localized file also.
You may also want to localize the following items in addition to the files that are addressed in this walkthrough:
Solution folder name
Outlook form region
Outlook ribbon controls
Before you begin, ensure that you have the following prerequisite tools:
An XML editor such as Notepad or Microsoft Visual Studio
Microsoft InfoPath Designer 2010 installed on your development computer, to modify the InfoPath template forms
The Code Sample: AdventureWorks2008 Declarative Outlook Solution that is included in the SharePoint 2010 SDK