Visualstudio-docs: Is the UTF-8 BOM A Requirement of the Solution File Format?

[aolszowka]

Based on this pull https://github.com/dotnet/cli/pull/8199 the CLI Tool expects there to be a UTF-8 Byte Order Mark (BOM) in the file. Creating a new solution from Visual Studio also seems to include the BOM. Is this expected?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 9177b266-5055-95d6-407f-ca4aad75257a
• Version Independent ID: 4586847b-d990-df3b-4cce-bd9a471eda33
• Content: Solution (.Sln) file - Visual Studio
• Content Source: docs/extensibility/internals/solution-dot-sln-file.md
• Product: visual-studio-windows
• Technology: vs-ide-sdk
• GitHub Login: @madskristensen
• Microsoft Alias: madsk

[msebolt]

@aolszowka Thank you for the question, assigning this to the author for further information.

[tfosmark]

@aolszowka Thanks for your question. Here are a few options where you might consider asking your question:​

https://social.msdn.microsoft.com/Forums/vstudio

https://www.stackoverflow.com

https://www.reddit.com/r/VisualStudio/

As well, you might also consider using the Report a Problem tool to report the issue.

[aolszowka]

Just to make it clear: You are saying that the place to get information about format produced, marketed, and serviced by Microsoft is the Community?

[aaronfranke]

Has anyone reported this to Visual Studio or MSBuild? Ideally those tools should interpret ANSI/UTF-8 files as UTF-8 by default since the encoding of all ANSI values is the same in UTF-8.