SEB3 fails to start if user's profile path contains Cyrillic characters about seb-win-refactoring HOT 8 CLOSED

Thanks for your detailed report. I am however unsure whether we can do anything to fix the issue, it appears like Windows / .NET require the system locale to be one that contains Cyrillic characters in order to allow those characters in a path.

Directory.CreateDirectory(directory);

This is the statement which fails, and there isn't much we can change here, we need to create the directory for log files if it doesn't exist. It really appears to be the case that .NET doesn't allow Cyrillic characters in the path if the system locale is e.g. English.

from seb-win-refactoring.

That's strange. .NET is unicode compliant and therefore should not rely on system's locale (system locale affects only non-unicode aware programs). I suppose a conversion from ASCII to Unicode occurs that causes the problem. I remember that at least one log file was created. So the locale should not be a problem.
Give me some time to get used to SEB's code and perform some tests if that helps. I'll give you feedback soon.

from seb-win-refactoring.

Of course, that would be great. Let me know if I can help in any way.

from seb-win-refactoring.

I've tested SEB with a a user that was typed in Cyrillic on my laptop. I can confirm SEB fails to start.
I've managed to clone latest source and compile SEB project. Interestingly the compiled version works with paths that contain Cyrillic chars.
It seems the issue is related only to version 3.0.1.163.

from seb-win-refactoring.

That would be very strange, as there haven't been any changes in that part of the code. Are you sure that the log directory did not exist when running the local build?

from seb-win-refactoring.

Let me perform the test again. I'll post the results here.

from seb-win-refactoring.

Any updates here?

from seb-win-refactoring.

Closed due to lack of feedback.

from seb-win-refactoring.