(In Visual Studio for Mac, there isn't a Break Mode tab, but the other behaviors are the same.) When that happens, Visual Studio doesn't highlight the current execution line in the editor or show any information in the Call Stack window.
#VISUAL STUDIO ON MAC OS DOCKER SUPPORT CODE#
The selected debug engine does not support any code executing on the current thread (e.g. On one of the repetitions of step 6, Visual Studio opens a Break Mode tab that says: (This is just a new template Xamarin.Android app with a minimal example AsyncTask.) Current behavior Test case: RepeatedBreakpointAsyncTask.zip Attempt to repeat steps 4 and 5 five times.After Visual Studio pauses on the breakpoint, run Debug > Continue.Tap the envelope icon button in the lower right of the app.Set a breakpoint on the first line of AsyncTask1.RunInBackground() (at MainActivity.cs line 16).Open the attached test case in Visual Studio.
But I'll submit it here in Mono first based on a guess that it might be possible to fix the issue by adjusting the debugger in some way. One thought I had based on the involvement of Android.OS.AsyncTask was that it might involve the Java interop layer. I'm not sure yet where the root of this problem is. This report is motivated by a secondary symptom I encountered when attempting to reproduce xamarin/xamarin-android#3222.