File Processing Does Preserve File Encoding
Currently, the application assumes that all project and solution files are encoded in utf-8 and include a byte order mark (BOM) at the beginning. This assumption can cause encoding issues for projects and solution files that are not encoded in utf-8. Additionally this assumption can add "noise" to the file diff when a BOM is added in files where it did not previously exist, or when the encoding attribute in the xml declaration is added when it did not exist previously or rewritten incorrectly in project files.
To resolve this issue the application should preserve the existence of the BOM and respect the encoding in the processed file.
+1
In addition, the tool should not convert line endings from CRLF to LF. This upsets Git, especially when autocrlf and safecrlf are enabled.
The tool shouldn't change white spaces either.