Step over an await call should send you to the next line (when the async operation is completed), today it sends you to the end of the method.
Internally the method is broken in many steps, as a state machine, but this should not mess with your debug experience.
A workaround is to set breakpoints after every await call in the method.
That's correct, the debugger steps on lines which are executed in the flow which in this case is closing }.
I know VS does "magically" switches to another thread with tiny tooltip of "The process or thread has changed since last step" but that's very bad if you want to debug the actual program flow. I think we should do something about the await continuation debugging but don't know what at the moment.
I know this is correct, but most of the times you want to debug the current method, line by line.
Today MonoDevelop have the "step over" option, maybe we could have another action, to step line, and that could be the default shortcut.
Another solution could be a small pop-up, that showed up when you step over the line. Presenting you the current step over option, and the new option to run to the next line.
Adding test code:
public static void Main (string  args)
var mainClass = new MainClass ();
mainClass.AsyncMethod ().Wait ();
}/*Stepping finishes here(after 4 seconds because of .Wait(), otherwise it's "instantly" stops here*/
private async Task AsyncMethod ()
await Task.Delay (4000);/*Breakpoint on this line and StepOver*/
Console.WriteLine ("Test");/*Stepping should finish here after 4 seconds*/