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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment