Bug 12396 - "Set Next Statement": method or operation is not implemented
Summary: "Set Next Statement": method or operation is not implemented
Status: RESOLVED ANSWERED
Alias: None
Product: Android
Classification: Xamarin
Component: Debugger ()
Version: 4.7.x
Hardware: PC Windows
: Normal enhancement
Target Milestone: ---
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2013-05-25 07:40 UTC by softlion
Modified: 2017-03-30 10:15 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 ANSWERED

Description softlion 2013-05-25 07:40:42 UTC
When debugging an android app, and you click the "set next statement" action used to move the current executing point elsewhere, then a dialog box appears :
---------------------------
Microsoft Visual Studio
---------------------------
Unable to set the next statement to this location. The method or operation is not implemented.
---------------------------
OK   
---------------------------
Comment 1 Miguel de Icaza [MSFT] 2013-05-27 06:21:07 UTC
We currently do not have plans to implement this.

Perhaps we can update the debugger engine to not show this UI in the first place.