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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment