Search Issue Tracker
By Design
Votes
1
Found in
2018.4
2019.4
2020.2
2020.2.2f1
2021.1
2021.2
Issue ID
1310073
Regression
No
Recompilation of all assembles is triggered when a managed plugin that is not auto-referenced is removed
How to reproduce:
1. Open the attached project ("case1310073.zip")
2. Select CustomAssembly/System.Runtime.CompilerServices.Unsafe.dll.
3. Notice that "Auto Reference" is disabled in its inspector.
4. Go to CustomAssembly.asmdef.
5. Notice that System.Runtime.CompilerServices.Unsafe.dll is listed in its dependencies.
6. Remove System.Runtime.CompilerServices.Unsafe.dll or move it outside of the project.
Expected results: Short compilation time. Only CustomAssembly.dll is recompiled
Actual results: Long compilation time. All assemblies are recompiled
Reproducible with: 2018.4.32f1, 2019.4.21f1, 2020.2.6f1, 2021.1.0b7, 2021.2.0a6
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note:
- CustomAssembly depends on this plugin.
- CustomAssembly is itself "Auto Referenced"
- When the plugin is removed, CustomAssembly is marked dirty
- As it is autoreferenced, dirtyness is propagated to the whole project.