Bug 6860 - Inspecting properties results wrong value
Summary: Inspecting properties results wrong value
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-09-03 10:10 UTC by Sebastian Krysmanski
Modified: 2016-08-03 15:23 UTC (History)
6 users (show)

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

Screenshot of the bug (337.18 KB, image/png)
2012-09-03 10:10 UTC, Sebastian Krysmanski
example project (11.86 KB, application/zip)
2012-09-03 10:11 UTC, Sebastian Krysmanski

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 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:

Description Sebastian Krysmanski 2012-09-03 10:10:16 UTC
Created attachment 2448 [details]
Screenshot of the bug

Inspecting a .NET property that's calculated on the fly results in wrong values when inspected in Visual Studio.

See screenshots. Here the variable test (type Vector3F) reports some weired value for "LengthSquared" (correct value would be 3.131698). Inspecting this value with the "Immediate Window" even results different value on every call.

The value itself seems to be correct, it's just displayed wrongly. It still makes debugging quite annoying.

I've attached an example project that let me reproduce the error. Restarting of the phone and Visual Studio didn't help.

I'm running Android 4.1 and Visual Studio 2010 with MfA 4.2.5 beta (latest version).
Comment 1 Sebastian Krysmanski 2012-09-03 10:11:59 UTC
Created attachment 2449 [details]
example project
Comment 2 Zoltan Varga 2012-09-18 12:29:35 UTC
What device are you using ? Does this happen with the simulator as well ?
Comment 3 Zoltan Varga 2012-09-18 13:09:50 UTC
Probably the same as:
but for android.
Comment 4 Sebastian Krysmanski 2012-09-19 03:28:39 UTC
I'm using a Galaxy Nexus. I didn't test it with the emulator but I confirmed the problem on a colleague's computer.
Comment 5 Zoltan Varga 2012-09-19 08:34:39 UTC
Should be fixed in mobile-master in c91fc1d6b68994c0c179c4ad99f1a656b14c61ec.
Comment 6 Sebastian Krysmanski 2012-09-19 08:43:44 UTC
This is the next 4.2.6 beta release?
Comment 7 Zoltan Varga 2012-09-19 08:46:03 UTC
No idea, can somebody comment on this ?
Comment 8 Jonathan Pryor 2012-12-08 00:29:04 UTC
The fix for this should be in the 4.4 release.