default.natstepfilter not working any more with VS 2022

Fabian 0 Reputation points
2025-01-28T20:24:52.9266667+00:00

The C++ debugger steps into all functions, regardless if they are excluded like this

<Function><Name>T*operator-></Name><Action>NoStepInto</Action></Function>

in default.natstepfilter

Developer technologies | Visual Studio | Debugging
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2025-01-29T06:31:57.0666667+00:00

    Hello fabian,

    Welcome to Microsoft Q&A forum.

    I created a c++ console app to do a quick test but found default.natstepfilter is working well.

    Here is my test result:

    After adding the function printGreeting in default.natstepfilter file, VS will skip the function when stepping into or pressing F11.debug

    For this issue, i have noticed a ReSharper Limiting

    Note that at the moment Visual Studio’s support for .natstepfilter files gets disabled if ReSharper C++ is installed.

    Please check if you have installed ReSharper extension, if so, try to temporarily disable it.

    What's more you can also use natjmc file instead. During C++ debugging, non-user code is skipped by default.

    Debug > Step Into (or F11) on non-user code steps over the code or runs to the next line of user code, if Step Into is called from non-user code.

    For example:

    <?xml version="1.0" encoding="utf-8"?>
    <NonUserCode xmlns="http://schemas.microsoft.com/vstudio/debugger/jmc/2015">
      <!-- Functions -->
      <Function Name="your function name" />
    </NonUserCode>
    
    

    Best Regards,

    Dou


    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.