http://blogs.msdn.com/winformsue/archive/tags/Windows+Forms+Globalization+and+Localization/default.aspxTags: Windows Forms Globalization and Localizationen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/winformsue/archive/2006/06/13/628824.aspxTue, 13 Jun 2006 02:28:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:628824Jay A. Allen0http://blogs.msdn.com/winformsue/comments/628824.aspxhttp://blogs.msdn.com/winformsue/commentrss.aspx?PostID=628824http://blogs.msdn.com/winformsue/rsscomments.aspx?PostID=628824Someone asked that question recently on an internal alias. Michael Kaplan, one of our localization gurus, says "not a week goes by" that he doesn't get that question. <a href="http://blogs.msdn.com/michkap/archive/2006/05/27/608625.aspx">Sadly, he has some bad news</a> for those looking to swap Japanese with French on the fly.<br><img src="http://blogs.msdn.com/aggbug.aspx?PostID=628824" width="1" height="1">Windows Forms Globalization and Localizationhttp://blogs.msdn.com/winformsue/archive/2006/01/31/521297.aspxWed, 01 Feb 2006 03:26:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:521297WinFormsUE0http://blogs.msdn.com/winformsue/comments/521297.aspxhttp://blogs.msdn.com/winformsue/commentrss.aspx?PostID=521297http://blogs.msdn.com/winformsue/rsscomments.aspx?PostID=521297<p>A recent bug (okay, it's WAY old and I only just got to it - my bad) makes it clear that we don't differentiate clearly enough in our documentation between forms-based resources and project resources. So here's the skinny. (I've added some of this information <a href="http://lab.msdn.microsoft.com/searchbeta/Redirect.aspx?title=Walkthrough%3a+Localizing+Windows+Forms&amp;url=http://msdn2.microsoft.com/en-us/library/y99d1cd3.aspx">to our walkthrough</a> for the next doc update.)</p> <p><em>Forms-based resources</em> are created when you set the <strong>Localizable</strong> design-time attribute on a <strong><a href="http://msdn2.microsoft.com/en-us/library/system.windows.forms.form.aspx">Form</a></strong> to true, and then set specific resources for various settings of the <strong>Language</strong> attribute. On Image properties, such as <strong><a href="http://msdn2.microsoft.com/en-us/library/system.windows.forms.control.backgroundimage.aspx">BackgroundImage</a></strong> on <strong>Form</strong> or <strong>Image</strong> on <strong><a href="http://lab.msdn.microsoft.com/searchbeta/Redirect.aspx?title=PictureBox+Class+(.NET+Framework)&amp;url=http://msdn.microsoft.com/library/en-us/cpref/html/frlrfsystemwindowsformspictureboxclasstopic.asp">PictureBox</a></strong>, when you use the snazzy new <strong>Import...</strong> button, you are importing a forms-based resource. (The UI calls it a "local resource".) Forms-based resources are weakly typed behind the scenes. Usually this is fine, as Visual Studio takes care of all the messy details for you of generating satellite assemblies and switching resources based on the current UI culture.</p> <p><em>Project resources</em> are created manually, by adding a new project resources file for a specific language. The plus side is that project resources are strongly typed, and thus easier to manipulate programmatically.</p> <p>What resource type should you use when? In general, use forms-based resources for anything that's form-specific; use project resources for error strings, or anything else that is application-global or that you need to assign programmatically. </p> <p>Here's an important tip, though: <strong>NEVER mix resource types for the same property!</strong> The bug I received was created because a customer tried to set the default <strong>Image</strong> on a <strong>PictureBox</strong> using a project resource, then set language variants using the <strong>Import...</strong> button (which uses forms-based resources). The result? We ignore the project resources entirely, so the default image never showed up. </p> <p>Let me know if this isn't clear, or if you feel the walkthrough could use even more detail. There's still time to get more text in before the next doc update!</p><img src="http://blogs.msdn.com/aggbug.aspx?PostID=521297" width="1" height="1">Windows Forms Globalization and Localization