May 18, 2008
A significant improvement in the web application localization have been done in VS2005. Now, the values are assigned automatically in a much better way.
To make your web page localizable:
1- Go to (Tools)
2- Click (Generate Local Resource)
3- wait until getting the following message:Finished creating resource content and adding ‘meta:’ attributes, the progress is now done.
you will find that a new folder named “App_LocalResources” have been created. In this folder you will find that a resource file have been created having the name <your page name>.asp.resx . In this file you will find that all of your controls properties have been added as entries in the resouce file but “Resource1” appended to the controls names.
Now, to add another language to your application you have to copy the resx file and add your culture name before the resx extention. (e.g. Default.asp.ar-eg.resx)
Localization have been improved in this version of Visual Studio but in needs more and more enhancement.
May 18, 2008
A lot of people always asking about how to localize ASP applications in .NET 1.1
Don’t expect too much from Visual Studio 2003 it provide nothing in this case.
if you want to build a localized web application you have to do it with your code.
and all of the localized controls MUST be server controls as you usually use a resource manager to retrieve the values from resource files and assign it to controls in runtime.
Take care that you need to retrieve the user culture (browser language) from the request object. Because the currentCulture is the server system culture.
You can made a loop to assign the resource entries to the controls properties but it will stay a very stupid process. Always there are keys forgetting and miss-spilling.
The conclusion: It was horrible believe me!!!
May 16, 2008
To deploy visual studio addin you have to place the AddIn file in this directory:
My Documents\Visual Studio 2005\Addins\
Open the AddIn file. You will see XML seems the following:
<?xml version=”1.0″ encoding=”UTF-16″ standalone=”no”?>
<Name>Microsoft Visual Studio</Name>
<Description>Sample Addin Description</Description>
Change the Assembly value to be the path of your addin DLL.
Change the full class name to be (<YourClassName>.Connect)
Then you will be ready to see your addin in the visual studio
May 16, 2008
To add a text from a resource file into your SharePoint ASPX page you have to place this code where ever you want this text to places.
– MyResource: is the resource file name.
-MyName: is the resource entry key.
Your resource files must be placed in this directory:
all resource files in this directory are copied to the global resources for every web application when it’s creating.
if the webapplication already exists place the resources files in this directory:
where <port> is the the web application port
May 16, 2008
In this post, I will discuss the logic contained in the data layer. The data layer logic is all in stored procedures and functions.
First, Let us discuss the logic for the Languages table. The following stored procedures may be defined on the languages table:
- AddLanguage: Add new language to the system. You must take care that this stored procedure not only adds a record in the languages table but it also adds a record for that language into all child tables.
- DeleteLanguage: Delete language from the system. You need to remove all the records related to that language from child tables. You have to check also if it’s the default language for any user then he/she has to change it.
- UpdateLanguage: Update the details for a language.
- GetLanguageDetailsById: Retrieves all the language data using language ID.
- GetAllLanguages: Retrieves all the languages supported by the system.
Then we can define a group of stored procedures on every multilingual parent-child tables:
AddRecord: This stored procedure is defined on the parent child records. It first adds a record in the parent table then adds its child record for a specific language and adds empty child record for each other languages. This stored procedure may use two other stored procedures or functions:
UpdateRecord: Updates a parent record and one of its related child so it needs to take a language parameter. Also, it needs another two stored procedures:
DeleteRecord: Deletes a record from parent table and all of its related child records. Again, it needs the two stored procedures:
- GetRecoredByLang: Retrieves the parent record and one of its children defined using the language paramenter.
- GetAllRecoreds: Retrieves the parent record and all of its children.
After developing these procedures for all tables, you need to move to the data access layer. In this layer, you have to make functions that allows you to connect to the database and access your tables and stored procedures. It’s so basic and straight forward so I will skip it.
Next time, I will talk about the business logic.