다음을 통해 공유

Tips for Deploying Localized Solutions

  • 아티클

Use the following tips to help you deploy localized intermediate declarative Outlook solutions for Microsoft Business Connectivity Services (BCS).

Applies to: SharePoint Server 2010

The following scenarios apply for installing or deploying one language build of the intermediate declarative Outlook solution to the environment:

  • Installing to a clean environment: To install the solution to a clean environment that has no other language build of this solution installed, you can just package the solution and install it.

  • Installing to an environment with an existing language build of the solution installed: Before you can install the solution to an environment that has another language build of this solution installed, you must uninstall that solution first, and then follow the steps to package the new solution and install it with the language build you want. For example, to install the Chinese version of the solution to an environment that already has the English version installed, you have to uninstall the English solution first, and then package the Chinese solution and install it.

The following scenario applies for installing or deploying more than one language build of the intermediate declarative Outlook solution to the environment, for example, if you want to install or deploy both the English build and Chinese build on one computer:

  • Installing or deploying more than one language build for one solution: To install or deploy more than one language build for a solution, perform the following steps:

    1. Edit the OIR.config file and provide a solution name and solution ID that are unique for each language, as shown in the following example.

      <SolutionSettings SolutionId="[DifferentIdPerLanguage]" 
                  SolutionDisplayName="[DifferentNamePerLanguage]"
                  SolutionVersion="[VersionNumber]"/>

    2. When you package the solution with the BCS Solution Packaging Tool, ensure that you use the same solution name as the one you specified in the OIR.config file.

      In this way, you can install all the different language builds for the solution, one by one.