Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Currently we still do some reflection at runtime, even when the static registrar is used.
We can improve this to make all reflection unnecessary. In fact I believe it's possible to make it so that nothing is done at startup, all information needed at runtime is loaded when needed, and not before.
This will minimize the minimum memory requirements for our apps (the less we do the less memory we use), and also make startup faster.
*** This bug has been marked as a duplicate of bug 33863 ***
oops, wanted to do the reverse - but they are already linked together (re-opening)
Additionally try to make the dynamic registrar code linker-friendly (so that it's linked away).
A consequence of removing all needs for reflection would be that the linker would be able to remove the ProtocolMember attributes.
Do we have an ETA for this ticket?
There's no firm ETA yet, but we're prioritizing it.
Unfortunately it's not a trivial fix, there's a fair amount of work required.
15.6 milestone turned out to be shorter than originally expected, new target is 15.7
This was done over several PR - the main one was #3495