WinForm internationalization:
Internationalization
I used WinForm internationalization to get up with some code (please refer to the post-Article ).
There is also an official international method recently found:
After each language is set, the designer automatically generates the corresponding resx files, such as Form1.resx (Default), Form1.zh-Hans. resx, Form1.en-US. resx, and so on.
Problem
After using the official method, I found the following problems:
Select
Before starting the project, you must select unofficial or official internationalization methods. switching between projects may lead to loss of the previous string resources.
Currently, I have old code. I suggest using unofficial methods. After all, the resx is controllable and the designer will not add anything to it. Only when the control name is restructured, the manual workload is heavy. (The workload during official restructuring is also high)
If you create a new project in the future, the official method may be okay, as long as you manually write the resource file to do it.
Reference:
1. Manual internationalization: http://www.cnblogs.com/codefish/p/4778269.html
2. Official WinForm internationalization: https://msdn.microsoft.com/en-us/library/y99d1cd3 (v = vs.71). aspx
3. Code switch official internationalization: http://www.dotnetcurry.com/showarticle.aspx? ID = 174