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 for Bug 59634 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
See bug #56489 for a test case.
Scenario: a big app, with one particular assembly which is enormous. The big app hits bug #1102 (too much code), but only for debug builds, most likely because the debug info for the enormous assembly is pushing it over the limit. The idea would be to make it possible to not generate debug info for specific assemblies (right now it's an either all or nothing choice), which could be used in this scenario to lower the executable size enough (and for the test case the app developer doesn't care about debugging the enormous assembly, since it wasn't his).