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
- SerializedPropertyChangeEvent is invoked when initially binding PropertyFields in custom Editor
- UI Panel is not visible when HDR and STP filter are enabled
- Crash on GfxDeviceD3D11Base::DrawBuffersIndirect when opening a specific project
- OnTriggerExit2D is called in Play mode when undoing component adding
- Builds fail with "Execution failed for task ':launcher:checkReleaseDuplicateClasses'" error when the newer version of the In-App Purchasing package is installed on a specific project
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.