Bug 33430 - Unable to set next statement in PCL project
Summary: Unable to set next statement in PCL project
Status: CONFIRMED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger (show other bugs)
Version: unspecified
Hardware: PC Mac OS
: Normal normal
Target Milestone: 15.6
Assignee: Joaquin Jares
URL:
Depends on:
Blocks:
 
Reported: 2015-08-27 13:03 UTC by Cody Beyer (MSFT)
Modified: 2017-10-04 16:37 UTC (History)
9 users (show)

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


Attachments
Screenshot of the menu command in question (4.14 KB, image/png)
2015-08-27 14:19 UTC, Brendan Zagaeski (Xamarin Team, assistant)
Details


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 33430 on Developer Community 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
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.
Related Links:
Status:
CONFIRMED

Description Cody Beyer (MSFT) 2015-08-27 13:03:29 UTC
### Description

It appears that support for setting next statement during debug is missing within PCL projects

### Steps to Reproduce

1. Create PCL Forms app
2. Set breakpoint with PCL project
3. Run project
4. Attempt to set next statement 

### Expected Results

You should be able to set next statement 

### Actual Results

The option is not allowed/greyed out

### Versions

Microsoft Visual Studio Professional 2015
Version 14.0.23107.0 D14REL
Microsoft .NET Framework
Version 4.6.00079

Installed Version: Professional

Visual Basic 2015   00322-40000-00000-AA453
Microsoft Visual Basic 2015

Visual C# 2015   00322-40000-00000-AA453
Microsoft Visual C# 2015

Visual C++ 2015   00322-40000-00000-AA453
Microsoft Visual C++ 2015

Visual F# 2015 RC   00322-40000-00000-AA453
Microsoft Visual F# 2015 RC

Application Insights Tools for Visual Studio Package   1.0
Application Insights Tools for Visual Studio

Common Azure Tools   1.5
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

GenerateUnitTest   1.0
Generates unit test code for methods in classes under test.

Microsoft Azure Mobile Services Tools   1.4
Microsoft Azure Mobile Services Tools

NuGet Package Manager   3.0.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

PreEmptive Analytics Visualizer   1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.

Xamarin   3.11.836.0 (ed5c750)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android   5.1.5.3 (f98871a95a479f6d71b3067b7e5834d41fcb2118)
Visual Studio plugin to enable development for Xamarin.Android.

Xamarin.iOS   8.10.4.0 (6db87c53c073f4af2f5247fb738a27ea08c094fd)
Visual Studio extension to enable development for Xamarin.iOS.

Xamarin.iOS Unified Migration   1.0
Automated migration for Xamarin iOS Classic projects to Unified

Xamarin.TestCloud.Integration   1.0
Early preview of Xamarin Test Cloud integration
Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2015-08-27 14:19:45 UTC
Created attachment 12666 [details]
Screenshot of the menu command in question

From the associated forum thread: http://forums.xamarin.com/discussion/49246/unable-to-set-next-statement-in-visual-studio-and-change-the-value-of-pcl-project-while-debugging
Comment 3 Zoltan Varga 2016-05-12 15:33:04 UTC
There is a ThreadMirror.SetIP () method in the Mono.Debugger.Soft api which does this.
Comment 4 Zoltan Varga 2016-05-17 15:40:44 UTC
-> reopen. Move off c7 milestone.
Probably should be moved to another product (VS?)
Comment 5 Marius Ungureanu 2017-09-26 10:32:16 UTC
Marking as confirmed. Set next statement works inside a console project, but not a PCL project.
Comment 6 Marius Ungureanu 2017-10-04 12:52:32 UTC
I have confirmed the actual cause of the issue. Unless the PCL assembly is loaded, Set Next Statement will not work. Doing Set Next Statement after the assembly has been loaded, it'll work.
Comment 7 David Karlaš 2017-10-04 16:37:17 UTC
I'm moving this to VS Extension since screenshot is showing VS not XS(VSfM)... Also this is now(it wasn't in 2015) supported in runtime and VSfM...

Not sure if VS extensions support it now.

What Marius was reporting as confirmed in VSfM was that we don't support setting into another functions/methods, which is not and won't be supported... To make it more clear to user I created this PR: https://github.com/mono/debugger-libs/pull/159