Question

DEBUGGING: F10 key is always stepping into automations, not over.. Why? How do I fix?

So I have a number of Automations that I call in sequence from a parent automation.. Pressing F10 I expect to step OVER the child automation, as I don't want/need to debug those routines. However Visual Studio steps INTO the automation(s) why? Without setting a million breakpoints, how can I ge the F10 Step over to work properly... It does in C#??

Correct Answer
October 8, 2019 - 6:04pm

F10 really just means "stop on yellow lines". F11 will go to both yellow and blue execution lines. Unfortunately, there's no way to step over an entire automation. Your suggestion of adding breakpoints after the automations you wish to pass by (and clicking F5) is really the only way to do that.

Comments

Keep up to date on this post and subscribe to comments

Pega
October 8, 2019 - 6:04pm

F10 really just means "stop on yellow lines". F11 will go to both yellow and blue execution lines. Unfortunately, there's no way to step over an entire automation. Your suggestion of adding breakpoints after the automations you wish to pass by (and clicking F5) is really the only way to do that.

October 16, 2019 - 12:01pm
Response to tsasnett

Sigh, Groan,  Ugh....   

I guess that's the way it is...

Bruce Hornsby