Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
2.0.2
Issue ID
VS-27
Regression
No
[Visual Studio] Visual Studio doesn't open .sln files when the project path contains non-Latin Unicode characters
How to reproduce:
1. Create a folder named "Пример"
2. Create and open a new Unity project in it
3. Open the Preferences windows by clicking Edit > Preferences
4. Go to the External Tools and select Visual Studio as the External Script Editor
5. Create a new Script by right-clicking in the Project window >Create > C# Script
6. Double click the newly created Script
Expected results: the Script opens together with the .sln file
Actual results: the .sln file fails to open
Reproducible with: 1.0.2, 2.0.2 (2020.1.0a15, 2020.1.6f1, 2020.2.0b3, 2021.1.0a1)
Not reproducible with: 2018.4.27f1, 2019.4.11f1 (1.0.11), 2020.1.0a14 (1.0.2, 2.0.2)
Notes:
-The full error message states: "These files could not be found and will not be loaded"
-This issue doesn't reproduce with VS Code or JetBrains Rider
-This issue doesn't seem to be dependant on the Visual Studio Editor package version
-The issue doesn't reproduce on any version when the Visual Studio Editor package is removed
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Compiled Shader code has self-assignments and redundant code in the Shaders that use "enable_d3d11_debug_symbols"
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
- "Unable to get the list of approved APIs." is thrown when testing the App Packages with Windows App Certification Kit
Resolution Note:
The user will have to report this to Microsoft. (Menu item Help > Send Feedback > Report Problem)
This is not something Unity is in charge of fixing.