. NET Chinese garbled Solution

Recently, I upgraded a project developed by VS05. After it is migrated to VS10, I will test run ~! I am illiterate. I don't know any Chinese characters! (Garbled) Description: This article uses the project to be changed to UTF8 encoding as an example. Solution 1. Modify Profile 1 <globalization requestEncoding = "UTF-8" responseEncoding = "UTF-8" responseHeaderEncoding = "UTF-8"/> done this step not solved, Next! 2. Add meta tag 1 to the page <meta http-equiv = "Content-Type" content = "text/html; charset = UTF-8"/> metadata is not resolved yet, Next! 3. Set @ Page command 1 <% @ Page ResponseEncoding = "UTF-8" Language = "C #" AutoEventWireup = "true" CodeFile = "list. aspx. cs "Inherits =" ExamineeStatus_list "%> the problem persists. Next! 4. Change. aspx and. aspx. cs file encoding method Note: select "Unicode (UTF-8 with signature)-code page 65001", scroll down and there will be "Unicode (UTF-8 without signature)-code page 65001, pay attention to identification. The token has never been resolved. Sorry! No, I'm switching to Google for you .... OK! After completing step 1, step 2 and Step 4, I have graduated from the Chinese department and re-recognized Chinese characters. Related Topic 1, about "UTF-8" and "UTF-8" "UTF-8" is a standard writing, if it is an English environment, can also be written as "UTF-8", in order to be strict, it is best to use the standard capital "UTF-8" 2. About the "UTF-8 with signature" and "UTF-8 without signature" the "UTF-8 with signature" encoding method will set a group of BOM at the beginning of the file (byte-Order Mark, byte sequence mark (ef bb bf (hexadecimal) to indicate that the file uses the UTF8 encoding method; the "UTF-8 unsigned" file is identified by the UTF-8 encoding principles.