Smart Step Into debugging in Rider

In a recent talk I gave about Rider’s debugger, one of the things I mentioned is that while writing code, we spend a lot of time in the debugger to validate our logic. Because of this reality, debugging should be as painless as possible. With Rider 2017.3 EAP, we’re introducing Smart Step Into to make debugging lines with multiple statements easier.

While in the debugger, we may sometimes reach a line of code that performs several method calls. Let’s take this line of code as an example:

PrintPeople(FilterPeople(people, BuildPredicate(person => person.Company.Country, "CZ")));

If we’d want to step into FilterPeople(), we’d first have to step through BuildPredicate() before we get to the method we want to debug:
Stepping into a method using Rider debugger

That works, but it does bring some overhead by having to mentally context-switch through another method than the one we really wanted to debug.

Smart Step Into solves this problem by letting us pick the function we want to step into. We can invoke Smart Step Into from the Run | Smart Step Into menu or by pressing Shift+F7:
Using smart-step into to not lose focus while debugging

When selecting a method using Smart Step Into, other methods will be ignored until code execution reaches the method we are interested in. This helps us keep focus on the task at hand, instead of having to follow an entire call chain we’re not interested in.

To give Smart Step Into a try, get a Rider 2017.3 EAP build! And make sure to check out our series about Rider’s debugger!

This entry was posted in How-To's and tagged , , . Bookmark the permalink.

One Response to Smart Step Into debugging in Rider

  1. Kevin Hahn says:

    Would it be possible to also have the lambda function be an option? Obviously it won’t always get executed but frequently it will be.

Leave a Reply

Your email address will not be published. Required fields are marked *