Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0f3
Issue ID
962192
Regression
No
SLN files generated by MacOS and Linux editors have two projects with the same name
Steps to reproduce:
1. Create a new project on a Windows machine
2. In Project window, right click on Assets folder -> Create -> C# Script
3. Create "Editor" folder and another C# script inside it
4. Repeat steps 1-3 on a Linux or MacOS machine
5. Compare {PROJECTNAME}.sln files located in the root project folder
Expected results: files are the same (Visual Studio version may differ), each project has a different project name.
Actual results: files are different, .sln files generated in windows have different project names, while Linux/macOS have the same.
Windows file contains this information:
Project("{...}") = "{PROJECTNAME}", "{PROJECTNAME}.csproj", "{...}"
EndProject
Project("{...}") = "{PROJECTNAME}.Editor", "{PROJECTNAME}.Editor.csproj", "{...}"
EndProject
macOS/Linux file contains this information:
Project("{...}") = "{PROJECTNAME}", "Assembly-CSharp.csproj", "{...}"
EndProject
Project("{...}") = "{PROJECTNAME}", "Assembly-CSharp-Editor.csproj", "{...}"
EndProject
Reproduced with: 5.6.4p1, 2017.1.2p1, 2017.2.0f3, 2017.3.0b6
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.