<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MIKE &#187; Globalization</title>
	<atom:link href="http://helios.ca/category/development/aspnet/globalization/feed/" rel="self" type="application/rss+xml" />
	<link>http://helios.ca</link>
	<description>Just another developer blog</description>
	<lastBuildDate>Thu, 10 Jun 2010 15:02:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>ASP.NET MVC and Localization</title>
		<link>http://helios.ca/2009/05/27/aspnet-mvc-and-localization/</link>
		<comments>http://helios.ca/2009/05/27/aspnet-mvc-and-localization/#comments</comments>
		<pubDate>Wed, 27 May 2009 20:50:15 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[ASP.NET]]></category>
		<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Developement]]></category>
		<category><![CDATA[Globalization]]></category>
		<category><![CDATA[MVC]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Photoshop]]></category>
		<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://helios.ca/?p=65</guid>
		<description><![CDATA[I live in Montreal &#8211; Canada, and here we have two officials languages, French and English, that&#8217;s why every website I build must be available in both languages. Building an ASP.NET MVC Website using Localization/Globalization is fairly simple and is pretty much like doing it on a plain old ASP.NET Website. We will start this [...]]]></description>
			<content:encoded><![CDATA[<p>I live in Montreal &#8211; Canada, and here we have two officials languages, French and English, that&#8217;s why every website I build must be available in both languages. Building an ASP.NET MVC Website using Localization/Globalization is fairly simple and is pretty much like doing it on a plain old ASP.NET Website.</p>
<p>We will start this example from a blanc ASP.NET MVC Website. This will be easier for you to follow. Now that you have your new ASP.NET MVC Website, create a new class and name it <strong>SetCultureAttribute.cs</strong> in a new <strong>ActionFilter</strong> directory and paste this code inside of it.</p>
<pre class="csharp" name="code">
using System;
using System.Collections.Generic;
using System.Globalization;
using System.Web;
using System.Web.Mvc;

namespace MvcApplication1.ActionFilter
{
    public class SetCultureAttribute : FilterAttribute, IActionFilter
    {
        public void OnActionExecuting(ActionExecutingContext
            filterContext)
        {
            string cultureCode = SetCurrentLanguage(filterContext);

            if (string.IsNullOrEmpty(cultureCode)) return;

            HttpContext.Current.Response.Cookies.Add(
                new HttpCookie("Culture", cultureCode)
                {
                    HttpOnly = true,
                    Expires = DateTime.Now.AddYears(100)
                }
            );

            filterContext.HttpContext.Session["Culture"] = cultureCode;

            CultureInfo culture = new CultureInfo(cultureCode);
            System.Threading.Thread.CurrentThread.CurrentCulture =
                culture;
            System.Threading.Thread.CurrentThread.CurrentUICulture =
                culture;
        }

        public void OnActionExecuted(ActionExecutedContext filterContext)
        {

        }

        private static string GetCookieCulture(ActionExecutingContext
            filterContext, ICollection<string> Cultures)
        {
            /* Get the language in the cookie*/
            HttpCookie userCookie = filterContext.RequestContext
                                                .HttpContext
                                                .Request
                                                .Cookies["Culture"];

            if (userCookie != null)
            {
                if (!string.IsNullOrEmpty(userCookie.Value))
                {
                    if (Cultures.Contains(userCookie.Value))
                    {
                        return userCookie.Value;
                    }
                    return string.Empty;
                }
                return string.Empty;
            }
            return string.Empty;
        }

        private static string GetSessionCulture(ActionExecutingContext
            filterContext, ICollection<string> Cultures)
        {
            if (filterContext.RequestContext.HttpContext
                                               .Session["Culture"]
                                                             != null)
            {
                string SessionCulture = filterContext.RequestContext
                                                .HttpContext
                                                .Session["Culture"]
                                                .ToString();

                if (!string.IsNullOrEmpty(SessionCulture))
                {
                    return Cultures.Contains(SessionCulture)
                                 ? SessionCulture
                                 : string.Empty;
                }
                return string.Empty;
            }
            return string.Empty;
        }

        private static string GetBrowserCulture(ActionExecutingContext
            filterContext, IEnumerable<string> Cultures)
        {
            /* Gets Languages from Browser */
            IList<string> BrowserLanguages = filterContext.RequestContext
                                                         .HttpContext
                                                         .Request
                                                         .UserLanguages;

            foreach (var thisBrowserLanguage in BrowserLanguages)
            {
                foreach (var thisCultureLanguage in Cultures)
                {
                    if (thisCultureLanguage != thisBrowserLanguage)
                        continue;

                    return thisCultureLanguage;
                }
            }
            return string.Empty;
        }

        private static string SetCurrentLanguage(ActionExecutingContext
             filterContext)
        {
            IList<string> Cultures = new List<string>
            {
                "en-CA",
                "fr-CA"
            };

            string CookieValue = GetCookieCulture(
                                            filterContext,
                                            Cultures);

            if (string.IsNullOrEmpty(CookieValue))
            {
                string SessionValue = GetSessionCulture(
                                                  filterContext,
                                                  Cultures);

                if (string.IsNullOrEmpty(SessionValue))
                {
                    string BrowserCulture = GetBrowserCulture(
                                                         filterContext,
                                                         Cultures);
                    return string.IsNullOrEmpty(BrowserCulture)
                             ? "en-CA"
                             : BrowserCulture;
                }
                return SessionValue;
            }
            return CookieValue;
        }
    }
}
</pre>
<p>Once this is done, we need to tell our controllers to use this attribute, to do this we could simply go on top of every controller and decorate it with <strong>[SetCulture]</strong> attribute. The down side with this is that we want the complete site multicultural, not just a few controllers or actions. To fix this problem we&#8217;ll make a <strong>BaseController</strong> which will inherit Controller and will be inherited from all our controllers.</p>
<p>To do this, create a new directory and name it <strong>Infrastructure </strong>and then add a new class called <strong>BaseController.cs</strong> in it. This class should contain the following code:</p>
<pre class="csharp" name="code">
using System.Web.Mvc;
using MvcApplication1.ActionFilter;

namespace MvcApplication1.Infrastructure
{
    [SetCulture]
    public class BaseController : Controller
    {
         // Anything you put here will be accessible
         // in every controllers
    }
}
</pre>
<p>As I said before, we need to tell every controllers to use BaseController, so open every controllers and change the inheritance from Controller to BaseController. As of now, your website knows how to handle localization!!! </p>
<p>What we need now, is a way to switch between french and english&#8230; To do this I simply created a new ASP.NET MVC View User Controller (CultureUserControl.ascx) in Views/Shared with the following code.</p>
<pre class="csharp" name="code">
<% if (Session["Culture"].ToString() == "en-CA") {%>
    <a href="/Home/SetCulture/fr-CA">[ Français ]</a>
<% } else if (Session["Culture"].ToString() == "fr-CA") { %>
    <a href="/Home/SetCulture/en-CA">[ English ]</a>
<% } %>
</pre>
<p>Then I added it to the masterpage, right next to the Log On link.</p>
<pre class="csharp" name="code">
<div id="logindisplay">
    <% Html.RenderPartial("LogOnUserControl"); %>
    <% Html.RenderPartial("CultureUserControl"); %>
</div>
</pre>
<p>Last, but not least, add a new <strong>Global.resx</strong> and <strong>Global.fr.rex</strong> in the App_GlobalResources folder. You can start with the welcome message in About &#8211; Index and call it using <strong>Resources.Global.Welcome</strong></p>
<p><img src="http://helios.ca/wp-content/uploads/2009/05/11.jpg" alt="11" title="11" width="547" height="423" class="alignnone size-full wp-image-107" /><img src="http://helios.ca/wp-content/uploads/2009/05/21.jpg" alt="21" title="21" width="547" height="423" class="alignnone size-full wp-image-108" /></p>
<p>You can find a working example of this tutorial <a href="http://helios.ca/wp-content/uploads/2009/05/ASP.NET.MVC.and.ocalization.zip">here</a>. </p>
]]></content:encoded>
			<wfw:commentRss>http://helios.ca/2009/05/27/aspnet-mvc-and-localization/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>C#.NET Localization with MasterPage</title>
		<link>http://helios.ca/2008/08/31/cnet-localization-with-masterpage/</link>
		<comments>http://helios.ca/2008/08/31/cnet-localization-with-masterpage/#comments</comments>
		<pubDate>Sun, 31 Aug 2008 17:02:29 +0000</pubDate>
		<dc:creator>Mike</dc:creator>
				<category><![CDATA[ASP.NET]]></category>
		<category><![CDATA[Developement]]></category>
		<category><![CDATA[Globalization]]></category>
		<category><![CDATA[Localization]]></category>

		<guid isPermaLink="false">http://helios.ca/?p=38</guid>
		<description><![CDATA[I recently started programming using C#.NET. The first thing I had to do with it, is make a complete website, kinda cool to learn about the language! At first it was easy, but then I had to localize the website for French and English. After hours of reading, I found a suitable solution written by [...]]]></description>
			<content:encoded><![CDATA[<p>I recently started programming using C#.NET. The first thing I had to do with it, is make a complete website, kinda cool to learn about the language! At first it was easy, but then I had to localize the website for French and English. After hours of reading, I found a suitable solution written by <a href="http://www.smart-soft.ch">Michael Ulmann</a>.</p>
<ol>
<li>Open up your Website in Visual Studio</li>
<li>Open up Global.asax and add these lines
<pre name="code" class="csharp">void Session_Start(object sender, EventArgs e)
{
    /*
     * Set the default language of the website
     * In my case it is en-CA, but you could put anything
     */
    Session["MyCulture"] = "en-CA";
}</pre>
</li>
<li>Create two links in your MasterPage.master
<pre name="code" class="csharp">&lt;asp:linkbutton
    onclick="changeCulture_Click"
    commandargument="fr-CA"
    text="Français"
    runat="server"
    id="btnSetFR"/&gt;
&lt;asp:linkbutton
    onclick="changeCulture_Click"
    commandargument="en-CA"
    text="English"
    runat="server"
    id="btnSetEN"/&gt;</pre>
</li>
<li>Add the Click Event to your MasterPage.master.cs
<pre name="code" class="csharp">    protected void changeCulture_Click(object sender,
       EventArgs e)
    {
        LinkButton senderLink = sender as
            LinkButton;

        Session["userCulture"] =
           senderLink.CommandArgument;

        Server.Transfer(Request.Path);
    }</pre>
</li>
<li>Create a new C# Class in App_Code, name it <strong>BasePage.cs</strong> and copy this code in it.
<pre name="code" class="csharp">
    public class MyPage : Page
    {
        protected override void InitializeCulture()
        {
            /*
             * Get the culture from the Sessions
             */
            string currentCulture =
                Convert.ToString(Session["userCulture"]);

            /*
             * Check if there's in a
             * culture in the Sessions
             * Otherwise, set the Default Culture
             */
            if (!string.IsNullOrEmpty(currentCulture))
                currentCulture = currentCulture;
            else
                currentCulture = "en-CA"; 

            /*
             * Apply the Culture to our thread.
             */
            Thread.CurrentThread.CurrentCulture =
                CultureInfo.CreateSpecificCulture(
                    currentCulture
                );

            Thread.CurrentThread.CurrentUICulture =
                new CultureInfo(currentCulture);

            base.InitializeCulture();
        }
    }</pre>
</li>
<li> Change the inheritance of all your web forms from Page to BasePage</li>
<li> Now all you need to do is create your Resources in GlobalResources and LocalResources Folders</li>
</ol>
<p>As I said, I learned this from an article posted on CodeProject by Michael Ulmann. If you would like to read the original article or download the source code, follow this <a href="http://www.codeproject.com/KB/locale/MasterPage_Localization.aspx">link</a></p>
]]></content:encoded>
			<wfw:commentRss>http://helios.ca/2008/08/31/cnet-localization-with-masterpage/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
