Bug 3202 - Watch window cannot evaluate UILabel .Text property
Summary: Watch window cannot evaluate UILabel .Text property
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 2.8.6
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-02-02 11:37 UTC by PJ
Modified: 2012-02-02 18:38 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description PJ 2012-02-02 11:37:13 UTC
Heyo,

Following this test case: https://testrail.xamarin.com/index.php?/cases/view/3339
On device.
Example project file is attached to test case.


Expected Result:
The immediate and watch windows recognize the UILabel's Text property and can evaluate it

Actual Result:
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'.
Comment 1 Jeffrey Stedfast 2012-02-02 13:51:40 UTC
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?
Comment 2 Sebastien Pouliot 2012-02-02 14:04:44 UTC
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 ;-)
Comment 3 Jeffrey Stedfast 2012-02-02 18:38:28 UTC
"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