Visual Studio automates resource generation per Web Form, but the task of synchronizing, managing, and versioning the resource files, and shipping them to translators for an application is cumbersome. The toolkit introduces a mechanism that supports this.
Visual Studio 2005 and ASP.NET 2.0 natively provide methods that streamline the process of retrieving resources programmatically. ASP.NET also automatically detects browser culture preferences, assigning the detected culture preference to the culture of the
The entire resource-management and translation process is easier to manage when there is a central resource repository. The Enterprise Localization Management Toolkit (the sample code, in beta as of this writing, accompanies this article) introduces a mechanism
that supports this central repository and single file creation, while still keeping the automatic resource generation capabilities of Visual Studio 2005. The Toolkit's features greatly simplify communication with the translators, reducing the number of
files to track while maintaining high developer productivity.
The Toolkit consists of three main parts:
** A central repository in an SQL Server 2005 database
** A Windows application for the technical manager
** A Web application for developers and translators
Developers use the Web application to modify the values of the resources they create or delete resources, while translators use it to review newly created resources and perform their translations based on the invariant culture value of a particular resource.
If translators do not have Web access to this application, they can use the resource editor utility that ships with the .NET Framework 2.0 SDK and work with a single resource file that administrators can generate using the Toolkit administration tool.
Administrators use the Windows application (The Toolkit Administration Tool) to import new resources into the database, and generate updated resource files for an application. The Administration Tool also supports adding a new culture to an application automatically,
generating the appropriate file for translation along with the resource files for the newly added culture. It tracks resource file generation, so you can know exactly when each file was generated.
In short, here are the features of the Toolkit:
** Microsoft SQL Server-based repository to store and manage the localized resources across all ASP.NET applications within an organization.
** Web-based resource management application for use by programmers, translators, and deployment personal.
** Support for the generation of loose resource files or satellite assemblies.
** Ability to automatically populate the localization database based on keys specified by a developer or Web designer by importing resource (.resx) files into the database.
** Ability to generate .resx files from the database after they have been translated and reviewed by the translators keeping track of the version.
1) Restore Localization Database backup to an instance of SQL Server 2005.
2) Restore Role/Membership Database backup to an instance of SQL Server 2005.
3) Run the aspsqlreg tool on the Role/Membership database.
4) Change the conneciton string in the Windows Application. Open the App.config file to change the entry LocalizationDBConnectionString to point to the Loclization
Database that was just created.
An example of the App.config file:
<?xml version="1.0" encoding="utf-8" ?>
<add key="LocalizationDBConnectionString" value="Data Source=END-2C3AFC0492A\SQLSERVER2005;Initial Catalog=Localization2;
User Id=Admin_Localization;Password=;" />
5)Enter the new connection strings in the Web.config file.
Add both Role/Membership cs and localization cs
Additional information about the initial stages of the project can be found at this DevX article: