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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.