Skip to main content

Multi Lingual page ASP.NET

Here the commented part would be the client side calling in ASP.NET file








using System;
using System.Collections;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Web;
using System.Web.SessionState;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.HtmlControls;
using System.Resources;

namespace NewMultiLingual
{
///
/// Summary description for WebForm1.
///

public class WebForm1 : System.Web.UI.Page
{
protected System.Web.UI.WebControls.Literal usernameLabel;
protected System.Web.UI.WebControls.TextBox username;
protected System.Web.UI.WebControls.Literal passwordLabel;
protected System.Web.UI.WebControls.TextBox password;
protected System.Web.UI.WebControls.Button login;

private void Page_Load(object sender, System.EventArgs e)
{
ResourceManager Rm1 = new ResourceManager("NewMultiLingual.Resource",System.Reflection.Assembly.GetExecutingAssembly());
usernameLabel.Text = Rm1.GetString("Username");
passwordLabel.Text = Rm1.GetString("Password");
login.Text = Rm1.GetString("Login");
// Put user code to initialize the page here
}

#region Web Form Designer generated code
override protected void OnInit(EventArgs e)
{
//
// CODEGEN: This call is required by the ASP.NET Web Form Designer.
//
InitializeComponent();
base.OnInit(e);
}

///
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
///

private void InitializeComponent()
{
this.Load += new System.EventHandler(this.Page_Load);

}
#endregion
}
}



Make Global.asax.cs



protected void Application_BeginRequest(Object sender, EventArgs e)
{


string lang = Request.QueryString["lang"];
string culturename = "en-US";
if (lang!= " ")
{
switch(lang)
{
case "f":
culturename = "fr-CA";
break;

case "ca":
culturename = "en-CA";
break;

case "ta":
culturename = "ta-IN";
break;

// default:
// culturename = "en-US" ;
}

}

CultureInfo Ci = new CultureInfo(culturename);
//Thread.CurrentThread.CurrentCulture = Ci;
Thread.CurrentThread.CurrentUICulture = Ci;

}


make appropriate additions in resource files

Comments

Popular posts from this blog

Task Parallel Library (TPL) and Akka.NET: Differences

Task Parallel Library (TPL) and Akka.NET are both powerful tools in the .NET ecosystem for handling parallelism and concurrency, but they serve different purposes and use different models of computation. Here are some key differences:s 1.    Actor Model vs Task-Based Model: Akka.NET is built around the actor model, where actors are the fundamental units of computation and they communicate by exchanging messages. TPL, on the other hand, is task-based. It's designed to make developers more productive by simplifying the process of adding parallelism and concurrency to applications. TPL uses tasks (which are independently executing work units) and provides various ways to control and coordinate them. 2.    Fault Tolerance: One of the key features of Akka.NET is its built-in fault tolerance. It has a "let-it-crash" philosophy, where the system is designed to self-heal from errors. If an actor fails, its parent actor can decide on the supervision strategy: either to resta

Extension Methods - Advanced

Here we will see how can we use the Extension Methods in advanced manner in other types Imagine you often need to retrieve items from a List based on a custom criterion that the built-in LINQ methods don't cover. Extension Methods for Lists: Filtering based on Custom Criteria And the output would be   Extending Enums: Displaying Descriptive Strings Output: Extending DateTime: Calculating Age     Output: The code samples can be found at https://github.com/oneananda/C_Sharp_Examples/tree/main/ExtensionMethods