[Blazor] The App.razor is not created default with UTF-8 encoding

[vulcanlee]

Because App.razor of Blazor project is not save with encoding default by UTF-8 (the default encoding is Chinese Traditional (Big5) - Codepage 950), cannot show any Chinese text of UTF-8.

To Reproduce this issue ( I also recording this problem and you can downlod Reproduce video without audio ), you can create a Blazor of server side project and open App.razor file to change as following.

<Router AppAssembly="@typeof(Program).Assembly">
    <Found Context="routeData">
        <RouteView RouteData="@routeData" DefaultLayout="@typeof(MainLayout)" />
    </Found>
    <NotFound>
        <LayoutView Layout="@typeof(MainLayout)">
            <p>抱歉，此地址沒有任何內容。</p>
        </LayoutView>
    </NotFound>
</Router>

To run this Blazor project and enter a not exist url, it will show incorrect context.

If I use function from menu : [File] > [Save App.razor as...] > [Save with Encoding...] and change Encoding property to "Unicode (UTF-8 with signature) - Codepage 65001" on "Advanced save options dialog"

Then re-run this Blazor project, the page is working fine as following:

My environment is Windows 10 Profession 1099 build 18363.535 of Chinese version

• ASP.NET Core version : 3.1
• Include the output of dotnet --info
• Visual Studio 2019 is 16.4.2

[pranavkm]

@ajaybhargavb didn't we fix this?

[glararan]

Confirming bug for 3.1. Did happen to me today

[ajaybhargavb]

@vulcanlee @glararan is this specific to App.razor or are you seeing this in all .razor files?

[glararan]

@vulcanlee @glararan is this specific to App.razor or are you seeing this in all .razor files?

Only in App.razor

[ajaybhargavb]

After investigation I found the following,
When VS first opens App.razor it defaults to Windows Codepage 1252 encoding. The same file when opened in VS Code defaults to UTF-8.
When I try to save the file with some unicode characters I get the following warning in VS,

Clicking yes saves it in the correct format and everything works as expected.

Yet, the core problem here is that Visual Studio thinks that App.razor is Codepage 1252 by default which we have no control over. I believe the reason this doesn't happen in other files is because they are stored as UTF8 with BOM where as App.razor is UTF-8 without BOM. So, to workaround this we'll change App.razor to be UTF with BOM and make it consistent with other files.

[glararan]

Im not so sure about dialog window. Didnt appear for me if I remember correctly. I had to resave it manually with UTF encoding

[ajaybhargavb]

@glararan what version of VS are you using? I'm on the latest 16.4.2.

[glararan]

@glararan what version of VS are you using? I'm on the latest 16.4.2.

16.4.0

[ajaybhargavb]

Found the real cause of this issue after discussing with @pranavkm. It is an issue with how dotnet templating works. This is now being tracked here dotnet/templating#2217.