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.
Following this test case: https://testrail.xamarin.com/index.php?/cases/view/3339
Example project file is attached to test case.
The immediate and watch windows recognize the UILabel's Text property and can evaluate it
The Watch window does not recognize lblOutput.Text
Additionally, the immediate window cannot evaluate it.
The line of code that changes the label also does not perform the action (The label isn't updated on the device) while in debugging mode. The label is correctly updated when the app is 'run'.
By changing the build options from "Link SDK assemblies only" to "Don't link", it now works as expected.
Sebastien: is the linker option expected to have this behavior?
Yes **if** the application code does not use UILabel::get_Text then it won't be part of the final (linked) binary - even if the UILabel::set_Text is present. That's what the linker is all about ;-)
"Fixed" this by adding an info icon next to the linker options which becomes a warning icon if the user enables both debugging *and* linker.
committed to md-addins git master