Files created by Visual Studio are generally considered to be UTF-8. However, when you generate a file using the Azure Functions template, the file is generated in ANSI.

[vijayrkn]

Creating the bug on behalf of the VS customer.

Details of the bug can be found here - https://developercommunity.visualstudio.com/content/problem/635626/visual-studio-2019-%E3%81%A6azure-functions%E3%81%AE%E3%83%86%E3%83%B3%E3%83%95%E3%83%AC%E3%83%BC%E3%83%88%E3%82%92%E4%BD%BF%E7%94%A8%E3%81%97%E3%81%A6%E3%82%AF%E3%83%A9%E3%82%B9.html

[ColbyTresness]

@soninaren

[soninaren]

Copied text from the original issue for context

Files created by Visual Studio are generally considered to be UTF-8. However, when you generate a file using the Azure Functions template, the file is generated in ANSI. Although this usually does not lead to a big problem, the character code will be scattered between the file generated using another template and the file.

Also, if you push code to Azure Repos, it will be garbled when you browse the code from the browser screen of Azure DevOps. In order to prevent this, please set the character code of the file generated by the template of Azure Functions to UTF-8.

[soninaren]

Looks like a valid ask moving to templates repo