Bug 6858 - 4.2.5 have some issue with VS2012 RC on Windows 8 RP when Debugging
Summary: 4.2.5 have some issue with VS2012 RC on Windows 8 RP when Debugging
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: Low enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-09-03 08:53 UTC by Imgen Tata
Modified: 2016-08-03 15:25 UTC (History)
7 users (show)

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 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 Imgen Tata 2012-09-03 08:53:50 UTC
#1. Performance is not acceptable. Taking too long to watch a variable, esp. complex object such as UI objects, when click to expand its properties, it would take tens of seconds to repsond
#2. Does not support compound variable name such as button.Text or button.Bottom.
Comment 1 dean.ellis 2013-06-05 12:00:17 UTC
Can you re-test this on the latest version please? There have been a number of improvements to the Debugger since last year.
Comment 2 PJ 2013-11-19 17:04:51 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:35:03 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.