It was fixed in .net 4.6.2 [0]
[0] https://blogs.msdn.microsoft.com/dotnet/2016/08/02/announcin...
[0] https://blogs.msdn.microsoft.com/dotnet/2016/08/02/announcin...
As I recall, this was marked "wontfix" in 2013: https://visualstudio.uservoice.com/forums/121579-visual-stud...
It's been _possible_ using the NT Unicode APIs since Windows 2000: https://msdn.microsoft.com/en-us/library/930f87yf.aspx
But other common first-party windows development tools can still have the problem: https://github.com/Microsoft/msbuild/issues/53
Was really happy to see it was finally fixed in .Net and the Anniversary update, and long, long overdue.