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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment