Add possibility to force encoding on project/solution level
This would be very useful to be able to force encoding on solution or project level and don't select it on per-file basis.
This would be great feature for internationally distributed developer teams and for open source projects.
Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.
- The Visual Studio Team
I agree this should be done, although preferably as part of a broader implementation:
"Store per-project source formatting settings with project properties"
Natan Vivo commented
Can't express how much this is needed when working with TypeScript. TypeScript won't compile files if there are non english characters and the format is not UTF-8, and this makes it very annoying to code if your project has non-english content (ex: comments).
Carlos Carrillo commented
This idea is very usefull, especially for web programmers where de character encoding is very important