Search Issue Tracker
Fixed in 5.1.0
Votes
0
Found in
4.6.3f1
Issue ID
676570
Regression
No
Unity fails to generate proper VS2013 solution when there's umlauts in the path to the Unity project
-e Unity fails to generate proper VS2013 solution when there's umlauts in the path to the Unity project
-repro:
- have unity project in path with umlauts
- switch platform to "windows store"
- select "unity C# projects" checkbox
- build project
- open resulting VS solution in VS2013
-> VS cannot resolve paths due to broken umlauts in path
example error:
C:\Users\Unity Technologies\Desktop\testumläut\builds\testumläut\testumläut.csproj : error : The project file could not be loaded. Could not find a part of the path 'C:\Users\Unity Technologies\Desktop\testumläut\builds\testumläut\testumläut.csproj'. C:\Users\Unity Technologies\Desktop\testumläut\builds\testumläut\testumläut.csproj
Comments (1)
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
- "Customize handled extensions" part in the External Tools settings tab is not aligned with other properties
- Editor Diagnostics foldouts do not open when clicked on the foldout title
- [UI Builder] Visual Elements are not placed at the mouse cursor position when Absolute Position Placement is enabled
- "Width" and "Height" text is misaligned with slider ends in Screen Match Mode Parameters section of Panel Settings Asset
- Editor does not quit when Editor is not in focus and any floating window is opened
fantastisch_
Mar 24, 2015 14:05
Süper!