Localization and Globalization in ASP.Net

Most websites on the internet are designed and developed to support a single language and culture, but making a website or web application to support different languages and cultures is not difficult and easy to implement in ASP.Net.

Globalization is the process of designing and developing applications that function for multiple cultures. Localization is the process of customizing your application for a given culture and locale. 

ASP.Net localizes an application through the use of resource files. Resource files are xml files with .resx extension. Resources can either be a global resource, in which it is accessible throughout the site and placed in App_GlobalResources folder in a website or a local resource which is specific to a page only and is placed in App_LocalResources folder. 

        

        In Visual Studio right click the website in solution explorer and select Add ASP.Net Folder then select App_GlobalResources. After that, right click the App_GlobalResources and select Add New Item in the list of items displayed in the dialog box then select Resource File and give it any name. The next thing is to create our language specific resource files. Each language requires different resource file. A resource file takes a key name & value pair, so all the resource files will contain the same key but the different values as the language translation.

We need to override the page's InitializeCulture() method and set the page UICulture & Culture property, this property determines which global or local resource to be loaded for the page. ASP.Net checks the languageid and cultureid combination on the browser to determine the resource file to be used in rendering contents to that browser. to see the detailed list of languages and cultures identification click here. CLICK HERE

         To watch the demonstration click here: WATCH VIDEO

Prof. Shardul P. Patil
profshardulp.patil@gmail.com

Partial Class

Partial Class:

            There are many situations when you might need to split a class definition, such as when working on a large scale projects, multiple developers and programmers might need to work on the same class at the same time. In this case we can use a feature called Partial Class.

            C# provides the ability to have a single class implementation in multiple .cs files using the partial modifier keyword. Each source files contains a section of the definition of class. When partial code is compiled on CLR, multiple classes or interfaces or struct with partial keyword will be compiled into single unit or it is considered as single class, interface and struct. All classes should be declared under one namespace scope only.

                 

                Suppose you have a "Student" class. That definition is divided into the two source files "Student1.cs" and "Student 2.cs". Then these two files have a class that is a partial class. You compile the source code then create a single class.

Advantages of Partial Class:

• Separate UI design code and business logic code for ease of working and understanding.
• Multiple developers can also work simultaneously like one creating logic and other working on designer part.
• It is also helpful to embed our custom logic code under framework auto generated code.
• Larger classes can be split into smaller classes for easy to understand and maintain.
• Interfaces can also split into multiple code to share it with multiple developers which further help in fast application development.

There are some points that you should be when you are developing a partial class in your application:

• You need to use partial keyword in each part of partial class.
• The name of each part of partial class should be the same but source file name for each part of partial class can be different.
• All parts of a partial class should be in the same namespace.
• Each part of a partial class should be in the same assembly or DLL, in other words you can't create a partial class in source files of a different class library project.
• Each part of a partial class has the same accessibility.
• If you inherit a class or interface on a partial class then it is inherited on all parts of a partial class.
• If a part of a partial class is sealed then the entire class will be sealed.
• If a part of partial class is abstract then the entire class will be an abstract class.

Example:

PartialClassFile1.cs:

public partial class MyPartialClass

{

    public MyPartialClass()

    {

    }

    public void Method1(int val)

    {

        Console.WriteLine(val);

    }

}

PartialClassFile2.cs:

public partial class MyPartialClass

{

    public void Method2(int val)

    {

        Console.WriteLine(val);

    }

}

MyPartialClass in PartialClassFile1.cs defines the constructor and one public method, Method1, whereas PartialClassFile2 has only one public method, Method2.  

Prof. Shardul P. Patil

profshardulp.patil@gmail.com