I have a utility class that has been thoroughly tested, and I do not want the VS debugger to step into any of its methods. I think I have heard of a way to mark something as not my code so that the Just My Code debugger setting causes the debugger to step over these method calls, but for the life of me I cannot recall what the class attribute is (nor can I successfully Google for it).

I know that I could separate this class into its own assembly and build it in release mode to alleviate the issue, but I would like to step into some of the assembly (and I would like to keep this class where it is).

Is this possible, or was I dreaming up this option?

Update

I did some testing with the two options (DebuggerStepThrough and DebuggerNonUserCode), and I found that DebuggerNonUserCode behaves exactly the same as the framework when having Just My Code enabled / 开发者_开发知识库disabled. The DebuggerStepThrough attribute always causes the debugger to skip the section marked with the attribute. For consistency's sake, I went with DebuggerNonUserCode.

You can use the DebuggerStepThrough attribute to skip over it.

You are looking for the DebuggerNonUserCode attribute.

If one was to judge by its name, the [DebuggerNonUserCode] attribute should do it, but it does not. So, the accepted answer is wrong, or at least it does not work for me in VS2017.

Judging by its name, the [DebuggerStepThrough] attribute was never intended to do what the question is asking for, and it comes as no surprise that it doesn't. So, the answer with the 20 upvotes is also wrong, or at least it does not work for me in VS2017.

What does work for me

is the [DebuggerHidden] attribute.

Go figure.