-
Notifications
You must be signed in to change notification settings - Fork 20
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
Unknown characters in GlobalSuppression.cs files #2
Comments
See the following Stack Overflow: http://stackoverflow.com/questions/17515768/git-messed-up-my-files-showing-chinese-characters-in-some-places Thanks @larrelandin |
It's not a known issue or something we have seen before. We will try it out and see if we can reproduce the issue |
As it turns out, we have seen it on same instances and it seems to be GIT related. We have provided a PowerShell script that can help you out. It's located with the release and named UnixToWindowsEOL.zip. |
@SorenKerrn That script seems to be designed only for items handled by TDS. This is another problem I am afraid. |
I think the bad characters have been checked into the repository somehow. I ran the UnixToWindowsEOL.ps1 conversion script with the following parameters:
But this did not resolve the issue. The earlier stackoverflow issue referenced by @brianhdk is spot on; it's definitely a UTF16LE encoding issue. |
We will take a look at it and make sure that the checked in source is in the correct format |
A new version of the source code files was pushed to the repository where the file formats have been fixed. It's tagged 8.1.478.2 |
This might be a local issue, but I've tried to clone the repository on different machines, and on every machine I'm unable to build the solution, because of strange chinese-looking characters in the GlobalSuppresion.cs file.
See the following screen-shot from VS: https://dl.dropboxusercontent.com/u/4142207/globalsuppression.JPG
Have you guys experienced this before - or know how to solve it?
It's the same issue if I download the ZIP file containing the source code. But the issue is not present in the previous release. Hope it helps.
Thanks
The text was updated successfully, but these errors were encountered: