1..Net Core Console Console Program
Codepagesencodingprovider.instance is not supported in the default System.Text in. Net Core,
System.Text.Encoding.CodePages.dll allows access to encoding providers that are not supported on the. Net Framework platform.
For more information:
https://msdn.microsoft.com/zh-cn/library/windows/apps/xaml/mt643899
Nuget:
Address: http://www.nuget.org/packages/System.Text.Encoding.CodePages/
Command:
Install-package System.Text.Encoding.CodePages
Usage examples:
class program{ staticvoid Main (string[] args) { // registering the encoding provider Encoding.registerprovider (codepagesencodingprovider.instance); Console.WriteLine (" Chinese content "); Console.WriteLine ("Hello world! " ); Console.read (); }}
2.asp.net Core MVC View Page Coding issues
In VS2017, the just-on-line version, in the Controller's action right-click Add View, the new view file encoding is ansii, by default in the browser to view Chinese is garbled.
Solution 1: Add a view in a new item by changing the way you add a view
Solution 2: The new view in VS changes the page encoding to UTF-8
File "Advanced Save" Modified page encoding
Note: In particular, "advanced Save" is hidden by default and needs to be added yourself in "Custom".
、
More:
Value transfer between ASP. NET Core MVC controller and view
. The use and finishing of Efcore in Netcore
VS code build. Netcore Development Environment (II)
. Net core Chinese coding problem collation