Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upTooling is not removing a dll that is no longer referenced by code unless you rebuild #5588
Comments
PureWeen
changed the title
Tooling is not removing a dll that is no longer referenced in code unless you rebuild
Tooling is not removing a dll that is no longer referenced by code unless you rebuild
Feb 11, 2019
This comment has been minimized.
This comment has been minimized.
sounds like the cache is not updated when an assembly is no longer needed (so an old copy might still be present and copied to the .app) |
PureWeen
referenced this issue
Feb 12, 2019
Closed
Referencing an assembly from linker.xml that isn't referenced in code will cause the dll to copy to app but not load into the domain #5589
rolfbjarne
added
bug
iOS
labels
Feb 12, 2019
rolfbjarne
added this to the Future milestone
Feb 12, 2019
This comment has been minimized.
This comment has been minimized.
Yes, this is how we currently behave, we don't keep track of assemblies that aren't included in the build anymore, so we don't know whether they should be deleted or not from the .app during incremental builds. |
This comment has been minimized.
This comment has been minimized.
I think you meant Build (or Run / Debug) but not Rebuild since
After a rebuild the file is missing. The sample still crash but with a
It's an old bug and was not an issue since Now those assumptions are changing with the interpreter so thanks for noticing and reporting it :) |
PureWeen commentedFeb 11, 2019
•
edited
Steps to Reproduce
Make sure to have linking turned off
Expected Behavior
Behavior before rebuild should be the same as after rebuild
Actual Behavior
A rebuild is required in order for the dll that's no longer referenced in code to not be included with the app
Environment
Example Project (If Possible)
PreserveTest.zip