Bug 15576 - (feature request) implement debugger visualizer on code editor
Summary: (feature request) implement debugger visualizer on code editor
Status: CONFIRMED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger (show other bugs)
Version: unspecified
Hardware: All All
: Lowest enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-10-22 02:24 UTC by Atsushi Eno
Modified: 2017-08-04 22:30 UTC (History)
1 user (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 for Bug 15576 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 original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Atsushi Eno 2013-10-22 02:24:05 UTC
We want something like CodeRush's debugger visualizer:
https://www.devexpress.com/Products/CodeRush/debug-visualizer.xml

briefly:
- show variables' values in the context method *on the code editor* (instead of another perspective).
- also make return value visible
- bonus if it can show some "future" values.
- expression explorer view that shows computation results for each branching node.
  - except expressions with side effect (I assume this requires XS to judge if an expression has side effect or not, which does not sound very easy.)
Comment 1 Atsushi Eno 2013-10-28 03:49:19 UTC
huh, bugzilla somehow dropped my summary text...