Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.2.21f1
2020.1
Issue ID
1221293
Regression
No
csc.rsp references do not work when used with custom assemblies
Steps to reproduce:
1. Open and run User-supplied project
Expected: no errors are thrown
Actual: errors are thrown
Reproduced in: 2018.4.17f1, 2019.2.21f1, 2019.3.3f1, 2020.1.0a24
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
- Sprite Atlas Samples throw multiple warnings when changing the original Editor verion
- Deleting 2D Lights while Lighting Explorer is open throws “GUI Error” and “NullReferenceException” errors in the Console window
- "Couldn't open file for reading" error occurs when running binary2text on a file larger than 2 GiB
- AssetReference Variable will default to Texture Asset Reference Type when no Asset Reference is set and it's duplicated in UI Builder
- Unable to open projects for a period of time when closing "Project not found" panel in any way
Resolution Note (2020.2.X):
This behaviour is unsupported by design. If you want to reference a custom assembly it must be located in the Assets or Packages folders, which we scan assemblies for.
You can also un-tick the "Override References" in the asmdef and reference your assembly from there, but it must be loaded.