Skip to content

Workaround template fix for incorrect file encoding when the first line is a conditional statement #18213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 15, 2020

Conversation

ajaybhargavb
Copy link
Contributor

Fixes #18058

This is a workaround for the issue dotnet/templating#2217.

@ajaybhargavb ajaybhargavb requested a review from pranavkm January 9, 2020 00:22
@Pilchie Pilchie added the area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates label Jan 9, 2020
@ajaybhargavb
Copy link
Contributor Author

ajaybhargavb commented Jan 10, 2020

Description

When creating a new Blazor project from template, App.razor is generated as ANSI instead of UTF-8. This is an issue with the templating engine which is tracked here. This PR contains the workaround until the underlying templating issue is fixed.

Customer Impact

Reported by two customers. Unicode characters in App.razor are not rendered in the browser correctly.

How found

Customer report

Test coverage

Manually verified the workaround. Working on adding a recurring test to be run by vendors.

Regression?

Yes, from 3.0 to 3.1

Risk

Low

@ajaybhargavb ajaybhargavb added the Servicing-consider Shiproom approval is required for the issue label Jan 10, 2020
@timheuer
Copy link
Member

Suggest a quick re-title of this to explain better. "Workaround template fix for incorrect code page when conditionals are first line"

@ajaybhargavb ajaybhargavb changed the title Workaround for #18058 Workaround template fix for incorrect file encoding when the first line is a conditional statement Jan 10, 2020
Copy link
Contributor

@mkArtakMSFT mkArtakMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Ajay!

@mkArtakMSFT mkArtakMSFT added this to the 3.1.x milestone Jan 14, 2020
@mkArtakMSFT mkArtakMSFT added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Jan 14, 2020
@mkArtakMSFT mkArtakMSFT modified the milestones: 3.1.x, 3.1.2 Jan 14, 2020
@mkArtakMSFT
Copy link
Contributor

This is approved by tactics for February release. I'll merge this when it's time.

@dotnet dotnet deleted a comment from wtgodbe Jan 15, 2020
@mkArtakMSFT mkArtakMSFT merged commit cba11d7 into release/3.1 Jan 15, 2020
@mkArtakMSFT mkArtakMSFT deleted the ajbaaska/workaround branch January 15, 2020 19:42
dougbu added a commit that referenced this pull request Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates Servicing-approved Shiproom has approved the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants