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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
fantastisch_
Mar 24, 2015 14:05
Süper!