Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
2017.1.0b9
Issue ID
920682
Regression
Yes
Reference to Assembly-CSharp.dll is generated instead of Assembly-CSharp.csproj in Assembly-CSharp-Editor.csproj
To reproduce:
1. Open the project, attached by the tester (badReference.zip) in 5.6.2f1
2. Open the file Assembly-CSharp-Editor.csproj
3. Find the refernece to Assembly-CSharp
4. Repeat 1 - 3, but open the project in 2017.1.0f1
Expected: reference is generated to the Assembly-CSharp.csproj
Actual: generated reference points to the Assembly-CSharp.dll
Due to this issue, Visual Studio Code functionality, such as Go to Definition, doesn't work properly.
Reproduced in 2017.1.0a3, 2017.1.0.b9, 2017.1.0f1, 2017.2.0b1
Did not reproduce in 5.6.2f1, 2017.1.0a2
Fixed in 2017.2.0b2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment